NARU SystemsCapabilities &
integrations.
Exactly what Voice AI and AI agents do today, what we connect per client, and what gets quoted separately. No fine print — if it's not tested for your account, we don't promise it.
What your Voice AI handles.
Answers inbound calls
Overflow and after-hours calls for one location on a standard U.S. local number, on the schedule you choose.
Answers approved questions
Hours, services, service area, and other FAQs you approve — nothing it hasn't been given.
Captures caller details
Name, contact info, and reason for calling, with names spelled back to confirm.
Notifies your team
A callback notification with the call details goes to one agreed destination.
Fallback routing
Near your spending cap, or if something fails, calls route to your team or voicemail as agreed.
Usage alerts & spending caps
Minutes are measured from call logs. You approve the cap; alerts fire before you reach it.
Calendar booking
Book into one supported calendar with one appointment type and standard availability rules.
Extra call flows
Add another call flow at the same location, sharing your minute allowance.
Multiple locations, multilingual, outbound
Extra locations, other languages, complex scheduling, and outbound campaigns.
What your AI agent handles.
Works in a chat channel
Message your agent the way you'd text an assistant. One named user and one channel to start.
Research & drafting
Research questions, draft emails, documents, and follow-ups for your review.
Tasks & to-dos
Tracks tasks and to-dos so follow-ups don't slip.
Files & summaries
Reads the files you share, summarizes them, and pulls out what matters.
Configured workflows
One trigger, one outcome, up to five steps — for example, a daily summary or an intake routine.
Custom connectors & data migration
New authentication methods, custom APIs, and data cleanup or migration.
Connects to the tools you already use.
Every connection is named in your proposal and tested end to end on your account before it becomes part of your service — one application, one account, the specific actions we list.
Your access. Your rules.
You keep control of access
You grant sign-ins and permissions through an approved setup process, and you can revoke them.
Draft ≠ send
Sending messages, changing records, and making bookings each need separately agreed permission.
Spending caps
Usage budgets are approved before launch. Raising a limit requires your approval.
Tested before launch
Success, failure, timeout, cap, and fallback tests run before anything goes live.
Human review
AI output may need review. Your team stays responsible for decisions outside the approved workflow.
Sensitive data
Regulated or sensitive-data workflows get a separate review and quote before we take them on.
Capability questions.
Does NARU connect to my email, calendar, or CRM?
Connections are scoped per client. We name the exact application and account in your proposal and test it end to end before it becomes part of your service. A connection doesn't include every possible action in that app — only the ones we list.
Can the AI send messages or change records on its own?
Only with separately agreed permission. Draft access and send/modify access are kept separate, and you approve write actions before they're turned on.
Can I take access back?
Yes. You grant the sign-ins and permissions and you keep control of them. Revoking access is part of every handoff plan.
What isn't included by default?
Custom API or authentication development, data migration, new apps or channels, extra locations, multilingual call handling, complex scheduling, and regulated or sensitive-data workflows are quoted separately.
Can Voice AI book appointments?
Calendar booking is an optional add-on for one supported calendar and one appointment type with standard availability rules. Complex scheduling or multiple systems are quoted separately.
Tell us your tools.
We’ll test the fit.
On a free demo we'll map your workflow and confirm exactly what we can connect for your account.
Book a Free Demo →