Missed-call text-back
A missed call from an unknown number creates a contact and sends a text within seconds, asking how you can help. Replies land in the GoHighLevel conversation.
CRM and automation
Turn every inbound call into a GoHighLevel workflow trigger.
Agencies and lead-driven businesses run their follow-up in GoHighLevel. This integration pushes 3CTel call, voicemail and SMS events to GoHighLevel by webhook, so a missed call from a new number becomes a contact, a pipeline stage and an automated text without anyone touching it.
ExampleView all team
Business number
+1 (416) 555-0198
Main numberActive call 00:24
IN
Inbound caller
+1 (905) 555-0142
Mute
Keypad
Hold
Add
End
Transfer call
Select a team member or department
Search people or teams
- Sales teamExt. 202
- Customer supportExt. 204
Your team
RC
ReceptionExt. 201
AvailableS1
Sales 1Ext. 202
On a callS2
Sales 2Ext. 203
AvailableSD
Service deskExt. 204
AvailableOM
Office managerExt. 205
In a meetingThe GoHighLevel integration is delivered by webhooks. 3CTel sends call, voicemail and SMS events to inbound webhook URLs in your GoHighLevel account, where workflows create or update contacts, move opportunities between pipeline stages and trigger automations such as a missed-call text-back. Data flows one way, from 3CTel into GoHighLevel. The integration is scoped during planning and confirmed before activation.
Last updated:
Integration type
- Integration type
- Webhook / event integration
- Availability
- On request — scoped during planning
- What is exchanged
- Missed call → webhook event → contact created and missed-call text-back sent
- Answered call → webhook event → activity on the contact; opportunity stage updated by rule
- Voicemail → webhook event with transcript → note on the contact and a task for the owner
- Inbound SMS → webhook event → conversation workflow continues in GoHighLevel
How it is set up
Choose events and outcomes
Decide which call, voicemail and SMS events to send and what each workflow does.
Create the workflows
Your GoHighLevel administrator builds webhook-triggered workflows and shares the URLs.
Connect and test
3CTel posts to the URLs; test calls and texts confirm contacts, stages and messages.
How it works: events out, workflows in
GoHighLevel workflows can start from an inbound webhook. 3CTel is configured to send a small, structured event to that webhook every time something happens on your phone system that you care about: a call starts, ends, is missed or abandoned; a voicemail is left and transcribed; a business text is sent or received.
Everything after that point is a GoHighLevel workflow you control. The event carries the caller's number, the number they dialled, the menu option or queue involved, the 3CTel user who handled it, duration, outcome and, for voicemail, the transcript. Your workflow decides whether to create a contact, add a tag, move an opportunity or send a message.
Because the connection is webhook-based, data flows one way. 3CTel does not read your GoHighLevel contacts or pipelines. That keeps the permission surface small and makes the integration straightforward to scope.
Business Phone
Reliable calling with routing your team will actually use.
Learn more: Business PhoneBusiness SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSCall routing
Decide who answers, in what order, and what happens when they cannot.
Learn more: Call routingEvents 3CTel can send
| Event | When it fires | Typical GoHighLevel action |
|---|---|---|
| Call answered | A call is picked up by a user or queue | Create or update the contact; log an activity |
| Call missed | A call rings out or the caller hangs up in queue | Missed-call text-back; create an opportunity; notify the owner |
| Voicemail received | A voicemail is saved and transcribed | Attach the transcript to the contact; create a task |
| SMS received | A text arrives on a business number | Continue a conversation flow; tag by keyword |
| SMS sent | A text goes out from the 3CTel app | Record the reply in the conversation history |
Common use cases
Pipeline by menu option
Callers who press 1 for new quotes become opportunities in the sales pipeline; callers who press 2 for existing jobs are tagged and routed to a service workflow.
AI receptionist hand-off
When the AI receptionist takes a message or books an appointment, the transcript and booking details arrive as an event and update the contact.
Agencies managing client sub-accounts
Each client's 3CTel numbers can post to that client's GoHighLevel sub-account webhook, keeping data separated per client.
What you need
- A GoHighLevel account, or agency account with sub-accounts, on a plan that includes workflows with inbound webhook triggers. The specialist confirms this with you.
- An administrator on the GoHighLevel side who can create the workflows and supply the webhook URLs.
- A decision about which events to send and what each workflow should do, especially for unknown callers.
- A phone-number format convention in GoHighLevel so incoming events match existing contacts reliably.
3CTel does not replace GoHighLevel's own phone or SMS features, and does not manage your GoHighLevel subscription. It sends your business phone system's events into the workflows you build.
Setup
Choose events and outcomes
With a specialist, decide which events to send and what should happen for each, including what an unknown caller becomes.
Create the workflows
Your GoHighLevel administrator creates workflows with inbound webhook triggers and shares the URLs with 3CTel.
Connect and test
3CTel is configured to post to those URLs. Test calls and texts on a temporary number confirm contacts, stages and messages behave as designed.
Questions from agencies and operators
Does GoHighLevel send anything back to 3CTel?
No. This integration is one directional: events leave 3CTel and arrive in GoHighLevel. Outbound texts triggered by a workflow are sent by GoHighLevel's own messaging, not through 3CTel, unless a separate SMS arrangement is scoped. Caller ID on the phone comes from 3CTel's own contact list rather than from GoHighLevel records.
How fast does a missed-call text-back go out?
The event is sent as soon as the call ends or is abandoned, and the workflow runs on GoHighLevel's schedule, typically within seconds. The timing you see depends on your workflow design and GoHighLevel's processing. Many operators add a short delay so a caller who redials immediately is not texted mid-call.
Can we send different events for different numbers?
Yes. Each 3CTel number, queue or menu option can post to a different webhook URL. An agency can route each client's numbers to that client's sub-account, and a single business can send sales-line events to one workflow and service-line events to another, with different tags and pipeline stages for each.
Privacy
Events pass directly from 3CTel to the GoHighLevel webhook URLs you supply, over an encrypted connection. Recordings stay on 3CTel; transcripts are included only if you enable the voicemail event. Retention on 3CTel is configured with you, and removing a webhook URL stops the flow of events to it immediately.
Related pages.
Business Phone
Reliable calling with routing your team will actually use.
Learn more: Business PhoneBusiness SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSAI Receptionist
Answers, understands and books — in English and French.
Learn more: AI ReceptionistAfter-hours calls
A plan for every call that arrives after closing, on a weekend or on a holiday.
Learn more: After-hours callsSmall Business
One business number, answered properly, from anywhere you work.
Learn more: Small BusinessFrequently asked questions.
No. GoHighLevel workflows with webhook triggers are built in its workflow editor, and the specialist walks your administrator through the event fields during setup.
Yes. The same event can post to a GoHighLevel webhook and to another system's webhook at the same time, which suits businesses that also run a helpdesk or a reporting tool.
Not by default; GoHighLevel sends from its own numbers. If you want one business number for calls and texts, a specialist can scope the SMS arrangement with you.
It is scoped per account and confirmed with you before activation. Nothing is billed until the events and workflows have been tested on a temporary number.
Tell us what a missed call should trigger.
Describe the pipelines and automations you already run. A specialist scopes the events, tests them against a temporary number and quotes the integration before activation.