From Ring to Lead: What Happens to a Phone Call Inside the CRM
A phone call is still the fastest way to win or lose a customer, and it is also the easiest thing to lose track of. Someone dials, the conversation ends, and all that is left is a memory in one person's head plus a scribbled note. In a CRM the call is data: who called, when, whether anyone picked up, how long it lasted and what happened next.
In Firmspace CRM you make calls straight from the browser. Twilio works as a native provider: account data, the phone number and the webhooks are configured by the CRM itself. Any other operator or PBX with SIP over WebSocket (Asterisk, FreeSWITCH, 3CX or a cloud PBX) is connected on the SIP provider tab, and the call itself goes from the browser directly to the provider. If both are connected, a provider switch appears in the dialler.
What exactly is stored about a call: the direction (incoming or outgoing), the interlocutor's number, the outcome and the duration. In Firmspace the outcomes are completed, missed, no answer, busy and failed. The call is not written into a separate list of calls on the side: it becomes an entry in the dialogue with that person, right next to messages, so the history of the relationship reads as one thread. The recent calls list in the dialler is built from the same entries, the last thirty of them.
Now the important part: the number becomes a customer, not just a line in a log. When an incoming call arrives, the CRM looks for a contact by that number. If there is no contact yet, a conversation is still created and named by the number, so nothing is lost. If the contact is added later, the next call attaches the dialogue to that contact automatically. In practice the chain looks like this: the phone rings, the number is recognised, the entry appears next to the whole previous correspondence, and a company name is visible instead of a set of digits.
A missed call does not wait for someone to notice it. If the outcome is anything other than a completed conversation, the CRM sends the team a notification that reaches people where they actually are: inside the platform and in Telegram, if the bot is connected. A completed incoming call is not counted as unread: someone already picked up, so there is no unread marker to clear. An unanswered call stays marked as missed, so it can be returned instead of quietly disappearing.
Every call also leaves a trace in the contact's activity history. The entry is short and factual: incoming call of such length, outgoing call, no answer, missed. So the customer card shows both layers at once: the detailed thread with the call entry in its place and a compact list of touches in the history, where a call is visible next to notes, tasks and e-mails. The salesperson opening the card before a conversation sees when the person was last contacted and how that attempt ended.
Firmspace also has an automatic lead filter, and it treats calls honestly: a missed call without content does not become a deal. A number that called and hung up is not a reason to create a card in the pipeline, because no one learned what the person wants. The filter records its decision in the log, and the call remains visible in the call history where someone can see it and call back. The rule is simple and deliberate: the pipeline fills with interested people, not with every missed call.
If the same number writes afterwards, the assessment happens on the message, exactly as for any other channel: the text is evaluated and, if it shows real interest in buying, a contact and a card in the first column of the pipeline appear, with the source marked as the channel the person came through. The calls themselves stay in the dialogue, so when the deal moves forward, the whole background — a missed call, a returned call, the message — is in one place and does not have to be reconstructed from memory.
The platform does not slow down the phone call itself: the call record is created in the background, so the provider's webhook is not kept waiting while the CRM writes to the database. This matters in the moment when several calls and messages arrive at once and nobody wants the dialler to freeze because a history entry is being saved.
What Firmspace deliberately does not do: it does not transcribe calls and does not write an automatic summary of a conversation. There is server-side speech recognition in the platform, but it is used for dictation in the assistant window; recordings of calls are not turned into text by themselves. The result of a conversation is you typing a note or creating a task, which takes a minute and keeps the meaning that a transcript would not give anyway. If you want to work by voice, dictation is the fastest way to record the outcome of the call.
By default the owner sees the SIP password in order to register in the browser — that is how the connection works, and there is no way around it. So telephony is set up on a separate internal number, and the provider's rules for who may call where are used. This is a technical limitation of browser telephony, not a CRM oversight, and it is worth saying plainly rather than hiding.
One more honest detail about the connection itself. Twilio is verified in production, while Telnyx and a number of SIP providers are integrated according to their documentation and tested against a simulated SIP server, so a specific operator is worth checking on your own account before the team depends on it. Providers that offer SIP only over UDP or TCP do not work from the browser: SIP over WebSocket (wss://) is required, otherwise an extra PBX has to stand in front.
And a limitation that comes from the architecture rather than from the CRM: with a SIP provider the record of an outgoing call is sent by the browser after the call ends, so in a closed tab the entry will not be saved. With Twilio the server writes the log from the webhook, so it arrives regardless. This is the reason the choice of provider is not only about the price per minute.
How to start: connect telephony in Settings, Integration, Call Provider. Twilio asks for the account data and the number; any other operator asks for the wss:// address, the SIP domain and the login. The CRM checks the data with the provider and stores it encrypted, so the credentials do not come back into the browser. Then calls work from the conversation window, incoming calls show up in a small panel, and every call ends up where work actually happens: in the dialogue with the client and in the history of the contact.
None of this makes a salesperson out of a CRM. The point is different: the phone stops being a hole in the customer history. It becomes one more tracked touch that a colleague can see, that a reminder can be built on and that management can count — without anyone having to remember what was said on Tuesday at five.