Computer telephony integration (CTI) connects your phone system to the software your agents work in, so a call arrives with the caller's record on screen and leaves a record of what was said and agreed. For a consumer brand, that record should be the customer's ticket and order, the same place their WhatsApp messages, emails and chats already sit.
CTI isn't the phone system itself; it's the link between the phone system and your helpdesk or CRM. A quick test of yours: when a customer who messaged yesterday calls today, does the agent see that message and the order before saying hello, and does the call's outcome reach the ticket afterwards?
In short
- CTI is the link, not the phone line. Your telephony provider supplies the numbers, the phone menu, the queues and the dialer; CTI passes each call's details to your helpdesk and writes the result back.
- Its core jobs are to identify the caller, show their record when the phone rings (the "screen pop"), log the call, and attach the recording, transcript and outcome to the right ticket.
- For an order call, the record that matters is the open ticket and the order, not just a name. Matching the caller to the right order is the hard part.
- You can check yours on last week's calls: how many were matched to a customer, joined an open ticket and had their outcome logged.
CTI vs your phone system: who does what
Most CTI guides list the phone menu, call queues and auto-dialers as CTI features, because their authors sell all of it together. If your phone line comes from one vendor and your helpdesk from another, separate the parts, because each stays with whoever supplies it.
| Part | What it does | Usually supplied by |
|---|---|---|
| Numbers and calling | Phone numbers, connecting calls, call quality | Your telephony provider or carrier |
| IVR | The phone menu ("press 1 for an order") that asks why the customer is calling | Your telephony provider or contact-center platform |
| Queues and ACD | Automatic call distribution: holds calls and passes each to an available agent | Your telephony provider or contact-center platform |
| Dialer and call controls | Answer, hold, mute, transfer; outbound dialling | Your provider's dialer or softphone |
| CTI | Matches the caller to a customer, shows their record, logs the call, attaches the recording and transcript, writes the outcome back | A connector between the phone system and your software, built by either side |
| Helpdesk or CRM | The ticket, the customer's orders and past conversations, and the actions agents take | Your helpdesk or CRM |
The phone menu has its own guide: interactive voice response (IVR). CTI adds the connection: the phone system knows a call is ringing, the helpdesk knows who the customer is, and CTI makes each tell the other.
How computer telephony integration works
Here is one inbound call, from ring to wrap-up:
- The call arrives. The IVR may ask why the customer is calling, and the queue passes the call to an available agent.
- The phone system sends an event. As the call rings, it sends the caller's number, her menu choice and the agent to the CTI connector. Cloud telephony providers do this through APIs and webhooks; older office phone systems (PBXs) used a CTI server and standards such as TAPI and CSTA.
- The caller is looked up. The connector searches your helpdesk or CRM for the number and finds the customer, her open tickets and her orders.
- The record opens on the agent's screen while the phone is still ringing. This is the screen pop.
- The agent handles the call. Call controls stay in the dialer or softphone; the agent reads and acts in the helpdesk.
- The call is written back. Time, duration and agent are logged on the ticket, the recording and transcript are attached, and the agent or an AI adds a summary and the outcome (the "disposition").
Outbound calls run the other way: the agent clicks the customer's number, the dialer places the call, and the same log is written back. If your team also makes calls, such as confirming COD orders before dispatch, see our guide to inbound and outbound calls.
Not every call comes through a phone number. WhatsApp's Business Calling API lets customers call a business's WhatsApp number. Businesses can call customers too, in most countries where the API is available but not the US or Canada (Meta: WhatsApp Business Calling API, checked 30 September 2026). Those calls belong on the ticket too, below the chat they followed.
Flowcall's phone integration works this way with Exotel, Ameyo, Ozonetel and Contaque. A call from your provider opens with the customer's context in the same workspace as your WhatsApp, Instagram, Messenger, email and Live Chat conversations, and is logged, recorded and transcribed on the ticket. Outbound works from the ticket too: agents click to call the customer through Exotel, Ozonetel or Ameyo. We built it so the phone team and the chat team work in one helpdesk and see the same customer history, instead of keeping call history where the chat team never looks.
What an agent should see when the phone rings
CTI guides describe the screen pop as "customer information". For a consumer brand, an order call is about one of three things: where the order is (WISMO, or "where is my order"), what went wrong with it, or when the money comes back. Before saying hello, the agent needs:
- The customer, matched to the caller's number, or a clear sign that there's no match.
- The open ticket and the latest messages on any channel. A customer who wrote on WhatsApp this morning and is now calling is chasing that message.
- The order: items, cash on delivery or prepaid, status and courier tracking.
- Returns and refunds in progress, with their dates.
- The last promise: what an agent told her, and by when.
- Why she's calling, if the phone menu asked.
With those on screen, the agent's first sentence can be an answer ("I can see the refund for your blender; it was started on Monday") instead of "Can I have your order number?" They're the same records behind every job in ecommerce customer service; CTI's job is to have them open before the agent speaks.
Matching the caller to the right order
A screen pop depends on the caller's number matching one in your records. For a consumer brand, these cases break that match:
- The order was placed with a family member's number, or a gift was sent to someone who now calls about it.
- The customer calls from an office landline or a second SIM.
- Several customers share one number, or one customer has several open orders.
Decide what happens before you switch CTI on:
- One match: open the customer's record and her most recent open ticket.
- Several matches: show the list and let the agent confirm the order with the caller.
- No match: open a new contact and let the agent search by order number or email, then add the number to the confirmed customer so the next call matches.
Never guess. Showing one customer's order to another is worse than asking a single question, so a match should be exact or confirmed by the agent.
A screen pop also stops at showing the record. If the agent still has to open the store admin, the courier portal and the payment gateway to act on it, the customer waits while they do.
This is the job we built the Zero-Tab Ticket for: everything an agent needs to answer and act on a case is in the ticket, so they don't open another tab. Customer 360 shows the customer's orders, delivery, payments, refunds and past conversations. Agent Assist summarises the ticket and fills the disposition. Pre-Filled Actions let the agent process a refund, create a replacement or update an order from the ticket, with the form already filled from the conversation and your systems.
One refund call, two ways
A customer returned a pair of trainers. The warehouse received them six days ago, but the refund hasn't reached her bank. She wrote on WhatsApp twice and got an automated reply each time. Now she calls.
Phone and helpdesk separate. The agent's screen shows a number and nothing else. He asks for her order number and searches the store admin, which says "returned". The refund status is in the payment gateway, so he puts her on hold to check: it was never started. He can't see her WhatsApp messages. He promises to "raise it with the team", types a note in the dialer and ends the call. That afternoon, the WhatsApp team replies to her second message by asking for her order number.
Phone and helpdesk connected. The call opens on her ticket. The agent sees both WhatsApp messages, the order, the date the warehouse received the return and a refund that hasn't started. He apologises, starts the refund from the ticket and tells her when to expect it. The call is recorded and transcribed on the same ticket with a summary, and a WhatsApp message confirms the refund after the call. When the WhatsApp team opens the ticket, the call is already there.
The phone line is the same in both versions. What changed is what reached the agent's screen when the phone rang, and what the call left behind.
In Flowcall's AI Helpdesk, what the call leaves behind is written for you. An AI summary of each call is linked to the right order, and Flowcall can send the customer a follow-up message after the call, so what was agreed on the phone reaches the next agent and the customer in writing. When the agent has finished the request on the call and nothing is pending, the ticket resolves itself; if the call missed a detail or a photo, the AI asks the customer for it over WhatsApp or email.
Five signs your calls aren't connected
Pull last week's calls and tickets and look for these:
- Agents ask callers for the order number when the customer has already written about that order on another channel.
- Call outcomes live outside the ticket, in the dialer's notes, a spreadsheet or an agent's memory.
- Recordings sit only in the telephony provider's portal, so quality reviews and escalations need a separate login and a search by time and number.
- A call opens a second ticket for an issue that already had one.
- You can't say what people called about. You know how many calls came in, but not how many were about late orders or refunds.
Two or more suggest the phone runs as a separate channel with its own records. Our guide to omnichannel customer service looks at the same problem across every channel.
Three ways to set up CTI
| Setup | How it works | Suits you if |
|---|---|---|
| A helpdesk with its own phone product | The helpdesk vendor sells numbers and a dialer; calls land on tickets natively | You want one vendor for the phone line and the tickets, and its phone service covers your countries |
| Your telephony provider connected to your helpdesk | Your cloud telephony provider or dialer stays; a connector links its calls to your tickets | You already have numbers, a dialer and an IVR that work, run by an in-house or outsourced calling team |
| A contact-center suite (CCaaS) | A contact-center platform runs calls, routing, IVR and workforce tools, with CTI into your CRM | The phone is your main channel, with a large calling team, outbound campaigns and shift planning |
If you're still choosing help desk software, check which of these it supports first. Our omnichannel call center guide covers the third route.
Whichever you choose, ask whether the vendor is still investing in the integration underneath. Salesforce has put Open CTI into maintenance mode ahead of its retirement in February 2028 (Salesforce: Get Started with Open CTI, checked 30 September 2026). ServiceNow says its Customer Service Management CTI plugin is being prepared for deprecation (ServiceNow: Integrating with CTI, updated 10 September 2026).
Flowcall takes the second route. Your provider keeps the numbers, the IVR and the dialer. The calls land in the same helpdesk as WhatsApp, Instagram, Messenger, email and Live Chat, with the customer's orders beside them and the same quality checks on every channel. If you'd rather buy the phone line and dialer from your helpdesk vendor, choose a helpdesk with its own phone product or a contact-center suite.
What to ask a CTI vendor
Take these to any demo:
- Which telephony providers and dialers do you connect to, and who built the connector? Ask to see it working with yours.
- How is the caller matched? By phone number only, or also by order number and email? What happens with several matches, or none?
- What appears when the phone rings? Ask for the open ticket, the latest messages from other channels, the order and any refunds, not just a name.
- Where does the call end up? On a new ticket every time or the customer's open one, and with which recording, transcript, summary and outcome?
- Can agents act during the call, such as starting a refund or a replacement, without leaving the ticket?
- What happens when the connection fails? Do calls still ring through, and are missed events logged?
CTI and AI: transcripts, summaries, quality checks and voice agents
Once calls are recorded on the ticket, AI can do three jobs that used to need a supervisor or reviewer to listen:
- Transcripts and summaries. A summary tells the next agent in a few lines what was said and agreed, without replaying the recording. Across many calls, transcripts feed speech analytics: what customers call about, and why.
- Quality checks on every call. Listening to a sample catches only what's in the sample. With transcripts, every call can be checked against your standards, such as the right refund timeline, or asking for details the customer already gave. See our guide to customer service quality assurance.
- Answering routine calls. Voice AI agents answer or place calls and hand over to a human agent when needed, so CTI's question becomes what the AI sees and what it passes on. Our guides to the AI call center, voice AI customer service and call center automation go further.
Flowcall's AI Auto QA audits phone calls from their recordings, alongside WhatsApp, Instagram, Messenger, Live Chat and email. It flags human agents who ask again for details the customer already gave, quoting the conversation in each finding.
Flowcall's Voice AI agent answers and makes calls on local numbers Flowcall provides in the countries you serve, alongside your telephony setup rather than through it, and follows the same workflows as the AI Agent on chat, checking and updating your systems as it goes. What it passes on is a recording, transcript and ticket for every call, so your team picks up with the whole call in front of them.
How to tell whether CTI is working
| Measure | How to count it | What it tells you |
|---|---|---|
| Match rate | Inbound calls matched to a customer record, divided by all inbound calls | Whether screen pops can work at all; a low rate points to missing or badly formatted numbers |
| Calls joined to an open ticket | Calls from customers with an open issue that were logged on that ticket, divided by all such calls | Whether the phone and messaging are one conversation |
| Outcome logged | Answered calls with a summary or disposition on the ticket, divided by all answered calls | Whether the next agent will know what was agreed |
| Repeat calls about the same order | Customers who call again about the same order within 7 days, divided by customers who called | Whether calls resolve the issue or only reassure |
| Asked to repeat | Calls where the agent asked for something already on the ticket, from quality reviews or a sample of transcripts | Whether agents use what the screen pop shows |
Average handle time should fall as lookups and wrap-up move into the ticket, but read it next to repeat calls: a shorter call that brings the customer back tomorrow hasn't saved anything. First call resolution is the other half of that check, and our guide to call center KPIs covers the wider set.
How to set up CTI, step by step
- List where calls come in: support numbers, the calling team's dialer, WhatsApp calls, and numbers printed on packaging or invoices.
- Store customer phone numbers in one format, with the country code, so caller ID can match.
- Write the matching rules for one, several and no matches.
- Decide what the screen pop shows, and test it on a COD order, a return and a refund in progress.
- Set call outcomes that match your request types, such as delivery delay, refund status and damaged item, so calls can be reported like tickets.
- Tell callers about recording. Add the notice to your call center script, check the consent rules where your customers live, and decide who can play recordings.
- Pilot with a few agents, check the measures above after two weeks, fix failed matches, then roll out.
How Flowcall handles phone support
Flowcall brings calls into the same AI Helpdesk your team uses for WhatsApp customer service, Instagram, Messenger, email and Live Chat. Calls from your telephony provider open with the customer's orders and past conversations, agents act and call customers back from the ticket, and calls leave a recording, transcript and summary where the next agent will look. AI Auto QA reviews calls alongside chats, so the phone gets the same checks as every other channel.
If you'd like to see a call open on a ticket with the customer's WhatsApp messages and order already there, book a demo.
Frequently Asked Questions
What does CTI stand for in telecom?
CTI stands for computer telephony integration: technology that makes phones and computers work together, such as showing a caller's record when the phone rings and logging the call. The same letters mean other things elsewhere, such as cyber threat intelligence in IT security.
What is CTI in a call center?
In a call center, CTI connects the phone system to the software on the agent's desktop. It identifies the caller, opens their record as the call arrives, lets agents control and place calls from their computer, and logs each call with its recording and outcome against the right customer or ticket.
What are some examples of telephony systems?
A telephony system is whatever connects your calls: a PBX (private branch exchange) in an office, a cloud telephony or VoIP provider that gives you numbers and a dialer in the browser, or a contact-center platform that adds IVR, queues and workforce tools. CTI connects any of these to your helpdesk or CRM.
What is CTI integration in Salesforce?
It's how a phone system connects to Salesforce so calls appear and are logged there. Salesforce's older toolkit, Open CTI, is a browser-based JavaScript API that telephony vendors use to build softphones inside Salesforce. Salesforce's developer guide says Open CTI is in maintenance mode, scheduled for retirement in February 2028, and recommends Salesforce Voice with Partner Telephony instead (checked 30 September 2026).
What is the difference between CTI and IVR?
IVR is the phone menu that answers a call and asks the caller why they're calling. CTI connects the call to your computer systems, and can pass the IVR choice to the agent's screen with the customer's record. They work together but are different parts, often from different vendors.
