Every call ends up where the work happens
A completed call, a missed call or a new voicemail creates or updates a record in your CRM, ticketing or practice system without anyone re-typing it.
APIs, Webhooks & Automations
Your phone system, wired into your software.
Call, SMS and voicemail events delivered by webhook, click-to-call and screen-pop for your own applications, AI receptionist actions that reach into your systems, and automation platform workflows — with keys and a sandbox issued per account.
- Webhooks for calls, SMS and voicemail
- Click-to-call and screen-pop in your apps
- AI agent actions against your systems
Example
Inbox+ New
AllCallsMessagesMeetingsVoicemails
- Incoming call+1 (416) 555-0198 · CustomerNew9:41
- AI receptionistUnderstands intent9:40
- Smart routingMatching to the best team9:38
- ConnectedSales team · Ext. 20100:189:37
- New messageProduct inquiry9:35
3CTel APIs, Webhooks & Automations connect a business phone system to the software the company already runs. Call, SMS and voicemail events are delivered by signed webhooks, custom applications get click-to-call and screen-pop, the AI receptionist can take actions in the customer’s systems mid-call, and automation platform workflows handle no-code connections. Keys and a sandbox are issued per account.
What changes for your business.
Staff dial from the screen they are already on
A number in your own application becomes a click-to-call link, and an inbound call pops the matching record before the greeting is finished.
The AI receptionist can do things, not just say things
During a call, the AI receptionist or voice agent checks availability, books the slot or looks up an order by calling your systems through the actions you define.
Automations built by your team, not a project
Common workflows run on an automation platform your team already uses, so a new rule is a few minutes of configuration rather than a development ticket.
Core capabilities.
Event webhooks
Call started, answered, missed, ended and recorded; SMS received and sent; voicemail left and transcribed. Each event is delivered as a signed HTTP request to endpoints you register per account.
Click-to-call
Start a call from a phone number in your own web or desktop application; the user’s desk phone or app rings, then connects the customer.
Screen-pop for custom apps
Inbound call events carry caller number, dialled number, queue and caller ID data so your application can open the matching customer record as the call arrives.
AI receptionist and voice agent actions
Define actions the AI receptionist or a voice agent can take mid-call — check a calendar, create a booking, look up an order, open a ticket — each calling your system with the parameters gathered from the caller.
Automation platform workflows
Connect 3CTel events and actions to a workflow automation platform to update sheets, send notifications, create tasks or trigger sequences without writing code. Platform connectivity is scoped during planning.
Send SMS and place calls from your systems
Send a text or start a call from your own application or workflow — order updates, reminders, callback requests — from your business numbers.
Keys, sandbox and scopes per account
API keys are issued per account with scoped permissions, and a sandbox environment is available for building and testing before touching live numbers.
Rate limits and security practices
Requests are rate-limited per key, webhooks are signed so your endpoint can verify the sender, and keys can be rotated or revoked from the admin console. Practices are reviewed with you during planning.
Common use cases.
Custom CRM or line-of-business app
A company with its own customer application adds click-to-call and screen-pop, and logs every call and voicemail against the account automatically.
Clinic booking from the AI receptionist
The AI receptionist checks open slots in the clinic’s scheduling system, offers two options, and creates the appointment — then texts the confirmation.
Service desk ticket from a missed call
A missed call to the support line creates a ticket with the caller’s number and transcript of the voicemail, assigned to the queue that was called.
Sales sequence from a first call
When a rep finishes a call with a new prospect, an automation platform workflow creates the contact, logs the call outcome and starts the follow-up sequence.
Setup and migration.
Integrations are scoped before keys are issued. A specialist maps the events and actions you need, confirms what your systems can accept, and sets up a sandbox so your developers or automation builders work against test numbers first.
Map events and actions
We list which call, SMS and voicemail events you need, which systems should receive them, and which actions the AI receptionist or your apps will trigger.
Issue keys and sandbox
API keys are created for your account with the scopes you need, and a sandbox with test numbers is provided for development.
Build and test
Your developers or automation builders connect endpoints and workflows. We help verify webhook signatures, screen-pop data and AI actions on test calls.
Move to production
Endpoints and workflows are switched to live numbers, rate limits and alerts are confirmed, and key rotation practice is agreed with your administrator.
AI in this product
AI through the API
The same AI events and agents your team uses are available to your own systems through API, webhooks and automation platforms, scoped with you in planning.
Transcripts, summaries and intents as events
Call, voicemail and message transcripts, summaries, sentiment and intent tags are delivered to your systems as webhook events or fetched through the API, so your own applications can act on them.
AI agents that read and write your data
AI Receptionist, chat and voice agents can query and update your own systems through endpoints you expose, with permissions and field mapping agreed before activation.
Custom workflow actions
A workflow can call your endpoint as one of its steps, so a conversation can trigger actions in a system nobody else integrates with, under the same approval modes and audit trail.
Common questions, answered directly.
What is a phone system webhook?
A webhook is a message the phone system sends to a web address you control when something happens — a call is answered, a text arrives, a voicemail is transcribed. Your application receives the event as an HTTP request with the details, verifies the signature, and does whatever you decide: update a record, open a ticket, alert a channel. It replaces polling and manual logging.
How does screen-pop work with a custom application?
When a call arrives, the platform sends an event containing the caller’s number, the number dialled, the queue and any caller ID data. Your application matches the number to a customer record and opens it for the person answering. With 3CTel the event is delivered by webhook or fetched by API, and the fields you need are confirmed during planning.
What can an AI receptionist do through an API?
Beyond answering and taking messages, an AI receptionist with defined actions can check a calendar, create a booking, look up an order or open a ticket while the caller is on the line. Each action calls an interface in your system with the parameters gathered from the caller, and the result shapes the next thing the receptionist says. Actions are defined and tested with you.
Learn more
- HubSpotCall, voicemail and SMS activity logged to HubSpot contacts and deals.
- SalesforceScreen-pop, click-to-call and call logging against Salesforce records.
- Appointment bookingBookings taken by phone, confirmed by text, and handed to a person when needed.
- Customer serviceThe phone workflow behind a support desk that answers, follows up and improves.
- UCaaS (Unified Communications as a Service)Phone, messaging, video and presence delivered together as one cloud service.
Learn more
Works with the tools you already use.
Integrations are scoped during planning based on your systems; availability is confirmed before activation.
- Webhooks & APICustom
- SalesforceCRM
- HubSpotCRM
- Zoho CRMCRM
- ZendeskHelpdesk
- FreshdeskHelpdesk
- GoHighLevelCRM
- SlackCollaboration
Related products.
AI Receptionist
Answers, understands and books — in English and French.
Learn more: AI ReceptionistBusiness SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSContact Centre
Queues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreCall Analytics
See what your phone traffic is actually doing — and staff for it.
Learn more: Call AnalyticsFrequently asked questions.
Not always. Webhooks, click-to-call and AI actions are aimed at developers; automation platform workflows can be built by an administrator without code. Which approach fits is decided during planning.
Call started, answered, missed, ended and recorded; SMS received and sent; voicemail left and transcribed. Events are registered per account against the endpoints you choose.
That is what AI actions are for. You define the action, the system it calls and the parameters, and the AI receptionist uses it mid-call. Whether your system exposes a suitable interface is confirmed during planning.
Yes. A sandbox with test numbers is issued per account so endpoints, workflows and AI actions can be built and tested before they touch live calls.
Each webhook request is signed so your endpoint can verify it came from your account, keys carry scoped permissions, and keys can be rotated or revoked from the admin console.
Workflow automation platforms that accept webhooks and HTTP requests can connect to 3CTel events and actions. The platform you use is scoped during planning and connectivity is confirmed before activation.
Map your integration with a specialist.
Tell us which systems your team works in and what should happen on a call, and we will scope the events, actions and workflows before issuing keys.