Every caller gets a person, a message or a callback.
Service businesses lose jobs to missed calls. This snapshot answers every call, connects the caller to your team when someone is available, and when nobody is, makes sure the caller hears back.
Team first
Calls ring your team line during business hours.
Six answers
Name, phone, reason, urgency and best callback time, saved to the contact.
Text and callback
A confirmation text and up to two callbacks, then a task for your team.
The snapshot contents.
Voice receptionist that greets, forwards and takes messages.
Answers inbound calls, tries the team, takes a message.
Texts, callbacks, AI call summary and follow-up tasks.
Runs when a callback is answered and connects the caller.
Reason for Call, Is It Urgent, Best Callback Time.
Your business name in every greeting and text.
Three workflows, one caller journey.
Text version of this diagram
An inbound call finds or creates the caller by phone number, and Sara greets them with the business name. The call is then forwarded to the owner's team line. If the team answers, the team gets a call-connected email. If nobody answers during business hours, or the call comes in outside business hours, the workflow marks which case it is and Sara takes a message: first name, last name, best phone number, reason for the call, whether it is urgent and the best time to call back, all saved to the contact. The contact is tagged missed lead, the team gets a missed-call or after-hours email with the details, and Sara confirms the message and says a text is coming before the call ends.
Text version of this diagram
When an inbound call ends, the workflow checks what happened. If the caller left a message (tagged missed lead), the tag is removed, the caller gets a message-received text, then a callback-coming text held until business hours, then up to two callback calls five minutes apart. An answered callback is noted and the callback conversation takes over; if both callbacks fail, a task asks the team to call back manually. If the call itself was missed, busy, sent to voicemail or failed, the caller gets a sorry-we-missed-you text and the team gets a task. Otherwise an AI step reads the transcript: if the caller hung up before giving their details they get a we-got-cut-off text and the team gets a task; if the call produced next steps the team gets them by email; if neither, a note records that no follow-up is needed.
Text version of this diagram
When a callback call is answered, Sara says she is returning the caller's call and tries the team line. If the team answers, the connection is noted. If nobody answers or it is outside business hours, Sara confirms the reason for the call and the best time to reach the caller, emails the team that the callback did not connect, confirms, and ends the call.
Seven owner steps make it yours.
- 1Set your business name
Update the Company Name variable.
- 2Enter your team phone and hours
On both forwarding steps. Default hours are Monday to Friday, 8 to 5 Eastern.
- 3Choose your caller ID
The number used for forwarding and callbacks.
- 4Connect an SMS number
For the four caller texts.
- 5Connect your email sender
And confirm the support address that receives team notices.
- 6Assign the agent to your business line
Calls to that number start the receptionist.
- 7Add your FAQs (optional)
Sara never guesses prices, hours or service areas; add a knowledge base if you want her to answer them.
Run the acceptance calls.
The call rings the team line and the team gets a call-connected email.
Six questions saved; missed-call email; message-received text; two callbacks at most.
After-hours email; message-received text now, callback-coming text and callback in business hours.
A we-got-cut-off text and a callback task.
A call-back-manually task and no third call.
Sara says she is returning the call and tries the team line.