This skill covers what happens after a call isn't answered. Who the number rings, and its menus and hours, are set in Business phone number and call routing. Do that first.
Every piece here reaches real people: the caller gets a text, the team gets email. Build it all, then show the person before anything is on.
Ask first
- Which number? Find the
phonerecord (data.phoneNumber, E.164) and note its mode:data.routingModeisivrfor IVR Menu, anything else is Direct Voice. - The voicemail greeting, in the business's words.
- Who on the team should hear about calls? Emails, and phone numbers if they want a text.
- The text back to the caller, e.g. "Sorry we missed you — we'll call back within the hour. {{business_name}}". And how often one caller may get it (default once an hour).
- Should a missed call become a lead? With which source and tags.
- Should texts to the number get an automatic reply? The words for open hours and for closed hours.
Steps
1. Phone & SMS: voicemail
Direct Voice number. The failover takes the voicemail. call_appengine PUT /phone/numbers/<phone sk> with:
{ "voiceConfig": {
"voicemailGreeting": "You've reached Harbor Grill. Leave your name and number after the beep.",
"failover": { "enabled": true, "action": "voicemail", "ringTimeoutSeconds": 20 }
} }The people ring for ringTimeoutSeconds, then the caller hears the greeting and a beep. A message can be 2 minutes long. failover is replaced whole, so keep any field already in it.
IVR Menu number. On its ivr_routing, set menuSettings.voicemailEnabled: true (and menuSettings.maxRecordingDuration in seconds, 120 when unset). Then use voicemail where it should happen:
- a forwarding group's
fallback: "voicemail"(when nobody in the group answers); - a menu option
{ digit, label: "leave a message", action: "voicemail" }; - a menu's
defaultAction: { action: "voicemail" }(after the caller presses nothing).
An IVR voicemail says "Please leave a message after the beep" in the line's own words. It has no custom greeting.
Hands on: where voicemail happens on this number.
Check: Direct Voice: the number's Phone Configuration › Call Handling shows Then… voicemail under the failover. IVR: the routing's Forwarding Groups and Menu Builder tabs on IVR & Phone System (/ivr).
2. Phone & SMS: tell the team about every call
The after-call email goes out for every call on the number, including missed calls and voicemails. Set it on the number (PUT /phone/numbers/<phone sk>, inside voiceConfig), or on its IVR routing (top-level fields, used first when set):
| Field | Value |
|---|---|
sendTranscript | summary (the call's details), full (plus the conversation word for word), or none |
transcriptToEmail | team emails |
transcriptToSms | team phone numbers |
The people assigned to the number get it too. With no recipient at all, it goes to the business's system email.
Hands on: the recipients. Check: the number's Phone Configuration shows the after-call setting and its recipients.
3. IVR & Phone System: missed-call actions
Missed-call actions live on the number's IVR routing, in missedCallActions. They are read for both modes. A Direct Voice number with no routing needs one to hold them. Create it as in step 4 of the routing skill, with routingType: "forward" and a forwarding group of the same people, so the line still works if anyone switches it to IVR Menu later.
Add the actions with update_record_partial ("data.missedCallActions": [ … ], the whole list). Write every field at the top level of the action:
type | Fields |
|---|---|
sms | name (unique; it keys the once-per-caller wait), to: "caller", message, cooldownMinutes (default 60), enabled: true |
email | to — a list of emails, subject, message (HTML) |
lead | leadSource (default missed-call), leadTags, leadAssignTo (a person's email), leadStatus |
Any action can have businessHoursOnly: true (see the warning below). In message and subject: {{caller}}, {{to}}, {{business_name}} (the routing's displayName), {{time}}, {{date}}.
When they run: when the people it rang didn't answer (no answer, busy, failed), and when a forwarding group runs out of people. A caller who then leaves a voicemail still gets the text.
- The text goes from the number that was called. Carriers block business texts from a number without SMS registration. Check the number's SMS Registration column on Phone & SMS. If it isn't registered, say so: the text won't arrive.
- A lead is made only if no lead has that phone number yet. It is named "Missed call +1…". It is written straight to the database, so it has no pipeline or stage and its owner gets no notice.
- Build these with the record tools, not the routing's Missed Calls tab. That tab saves what you type under
config, where the line doesn't read it. A text made there sends "Sorry we missed your call!" whatever it says, and an email made there sends nothing. The tab shows actions made here with empty boxes. That is expected. Don't retype them. businessHoursOnlyreads the server's clock, not the business's time zone. Leave it off unless the server and the business share a zone.automationdoesn't start an Automation. It only wakes AI Assistants that listen for missed calls.emailwithtoas one string (not a list) sends nothing.
Hands on: the routing's sk.
Check: get_record on the routing: missedCallActions holds each action with its message and to at the top level.
4. IVR & Phone System: auto-reply to texts (optional)
Only if the person asked. Find an sms_routing whose phoneNumbers has the number. Otherwise create_record on sms_routing:
| Field | Value |
|---|---|
name / displayName | e.g. main-texts / "Main line texts" (name is part of each reply's wait key, so always set it) |
phoneNumbers | ["<phoneNumber>"] |
enabled | true |
autoReply | { enabled: true, normalHoursMessage, afterHoursMessage, holidayMessage, cooldownMinutes } |
businessHours | same shape as the IVR's (enabled, officeHours, holidays) |
optOut | { enabled: true, confirmationMessage: "You're unsubscribed. Reply START to rejoin." }. STOP, UNSUBSCRIBE, CANCEL, END and QUIT are caught first. |
Messages can use {{sender}}, {{business_name}}, {{day}}, {{time}}. The reply goes back at once, at most once per sender per cooldownMinutes (default 60).
Text business hours also read the server's clock and date, not the time zone on the rows. On a server in UTC, a 9–5 Chicago day switches to the after-hours reply five or six hours early. Say so, and offer one reply for all hours (businessHours.enabled: false) instead.
Keywords, multi-step reply flows and handing texts to an AI assistant are in the same record. See the SMS routing editor on /ivr.
Hands on: the SMS routing's sk. Check: it is listed on the SMS Routing tab of IVR & Phone System, with the number.
Stop: switch it on
Show the person, in plain words:
- the voicemail greeting, and after how many seconds it starts;
- the text back to callers, the number it comes from, its SMS registration, and how often one caller can get it;
- the team emails or texts, and that they come for every call;
- the lead it creates, if any;
- the text auto-replies and the hours they follow.
Ask for a yes. Until then, keep the missed-call actions enabled: false and the SMS routing enabled: false. After it, set them true (update_record_partial). The voicemail failover and the after-call email are on from the step that saved them. If the person says no, set failover.enabled: false and sendTranscript: "none" again.
When it's done
Tell the person:
- where voicemail happens, and where to listen: Phone & SMS › Call Logs › the call;
- who gets the after-call email or text;
- the missed-call text, the lead rule, and whether they are on;
- the text auto-reply, if any, and the hours it follows;
- what's missing for the texts to arrive (SMS registration).
What it can't do yet
- A Direct Voice voicemail's transcript is lost. The audio is kept by the phone provider and plays from the call's detail on Call Logs. The text Twilio makes of it is never saved, and the recording isn't marked on the call log, so it doesn't show under Recordings & Transcripts. IVR voicemails are saved with their transcript.
- No voicemail email with the recording.
menuSettings.voicemailEmailon an IVR routing is saved but never used. The after-call email in step 2 is the notice. It can arrive before the voicemail's transcript. - Nobody assigned, nothing taken. A Direct Voice number with no one assigned plays its unassigned greeting and hangs up. The failover, voicemail and missed-call actions don't run.
- One greeting. The IVR voicemail can't play a custom greeting. Use a menu greeting before it, or Direct Voice.
Don'ts
- Don't turn on texts to callers without a yes, and don't promise a callback time the person didn't give.
- Don't use the routing's Missed Calls tab to write the actions.
- Don't send
emailactions withtoas a single string. - Don't put two enabled SMS routings or IVR routings on one number.