Platform · Inbound
Your AI answers real phone calls on a real number.
A customer dials your number; your agent picks up. Inbound routing matches the number to the agent automatically. India-ready via VoBiz, global via Twilio and Plivo.
Problem · Solution
The problem today
A missed call isn't a missed call — it's a missed customer. The phone rings while your receptionist is mid-walk-in, while your support desk is at lunch, on a Sunday afternoon when your scheduler is closed. Every dropped call goes somewhere else, and the lead, the booking, the support escalation goes with it. Standard fixes — voicemail, callback queues, IVR trees — all push the work onto a human who isn't there. Vocily AI picks up instead.
How Vocily AI handles it
Real number, real pickup
Bring your number (VoBiz, Twilio, Plivo) — or get one. Your agent answers every call. No 'press 1 for sales' menus, no voicemail.
Number-to-agent routing
Each inbound number maps to a specific agent. One workspace can host a sales line, a support line, and a billing line — different agents, different knowledge, all on the same workspace.
Business-hours enforcement
Timezone-aware weekly schedule plus a holiday calendar. After-hours callers hear your configured closed message and a graceful disconnect — not a generic voicemail.
Max call duration cap
Set a per-agent ceiling (1–30 minutes). Calls past the limit get a clean goodbye and disconnect. Predictable cost, no runaway sessions.
Inbound fallback message
If the agent fails to initialise or hits an unexpected state, the caller hears the fallback line you configured — never a dead silence or a dropped call.
BYOC carriers
Vocily AI layers on top of your existing carrier. India-friendly via VoBiz, global via Twilio and Plivo.
What's in it
What inbound ships with.
The operational primitives you need to run a phone line on AI — without losing control over who picks up, when, and what happens if things go sideways.
Pickup behaviour
- Number-to-agent
- Each inbound number maps to exactly one agent. Workspace can host many.
- Conversation start
- Bot greets first, or wait for caller to speak — configurable per agent.
- Consent placement
- Before greeting, after greeting, or skipped — DPDP-aligned recording-consent line.
- First-touch latency
- Agent picks up immediately. No 'connecting your call' delay.
Operating window
When the agent answers — and what happens when it doesn't.
- Schedule
- Per-day, per-timezone weekly schedule.
- Holiday calendar
- Block specific dates with a custom message.
- After-hours line
- Configurable spoken message + graceful disconnect.
- Edge holidays
- Easy to override the schedule for a single day.
Guardrails
Keep cost and behaviour predictable.
- Max call duration
- 1–30 minute ceiling per agent.
- Graceful timeout
- Spoken goodbye before disconnect — no abrupt cutoff.
- Init-failure fallback
- Configured spoken message if the agent can't start a session.
- Unexpected state
- Same fallback line — the caller never hears dead air.
Carriers (BYOC)
Bring your own telephony stack. We don't lock you into ours.
- VoBiz
- India-friendly carrier — fastest path for Indian numbers.
- Twilio
- Global coverage.
- Plivo
- Global coverage.
- No markup
- Per-minute pass-through. You pay what your carrier charges.
Common questions
What teams ask before they switch.
Yes — when escalation rules fire, the agent transfers to a configured destination (team-line, on-call rotation) with the conversation context summarised for the human picking up.