One phone for the whole session, shared by every screen that can start a call — a contact row, a pipeline card, the reply box, the callback list. It rings when someone calls your line and dials out showing your business number. If the browser blocks the microphone, it says so instead of failing quietly. One system for the whole post-frame business — the phone is in it, not bolted on — so every call already knows whose job it is.
Also called: softphone · call from my computer · browser calling · dialer · make calls in the CRM
Calls placed and answered inside the product, logged against the customer
The phone is part of the software, not a handset the business cannot see. Every call becomes a record — who, when, how long, whether it was recorded, and why it was missed — and the customer's history is on screen the moment they pick up. A call taken on a personal cell leaves the business nothing but somebody's memory of it.
A price gets agreed on a call from the truck, and six weeks later the only surviving version of that conversation is one person's memory of it.
The recents list is built around the question that actually gets asked afterwards — not whether somebody called, but which way it went and why it never landed — so a missed call carries its reason and the recording plays on the row itself, in a list anyone in the shop can open.
The phone sits over your work rather than being a page you go to
Try itDrag it anywhere and it stays where you put it. It shrinks to a bar while a call is live, and to a single puck when it is not — or drop it into the sidebar and it becomes an ordinary menu row. On a phone screen there is no puck at all; the header icon is the whole thing. A full-page dialer makes you leave the estimate the call is about.
Mid-call the customer asks what the porch adds, and the estimate is sitting behind a full-page dialer you would have to navigate away from to read.
Where a phone belongs depends on the screen and the person holding it, so that choice is not made for you: it stays where you dragged it the next time you sign in, collapses to a puck between calls, and can be put away in the sidebar entirely. The trade-off is a floating thing that can cover something — so one dragged value is stored, the panel is derived from it, and the whole dock is clamped back on screen when the window changes size.
A ringing call can be answered from any screen, and Silence is not hanging up on them
The incoming call arrives on its own layer above everything else, naming the caller where we know them — whatever you had open, and wherever the phone was parked. Silence stops the ringing on your screen while the caller rings on through to voicemail. Decline sends a rejection down the line, and plenty of people can tell they were cut off by a builder they were trying to give money to.
A homeowner rings while you are three windows deep in a takeoff, the ring goes unnoticed, and by dinner they have called somebody else.
Two buttons would force a choice between letting it ring forever and cutting a caller off, so there are three — and the line under them explains Silence while the phone is still ringing, instead of leaving it to be learned the expensive way. The banner is drawn outside the dock entirely, because Answer that only exists while a panel happens to be open is not an Answer button.
A second call never takes over the one you're on
Another call coming in while you are talking does not touch the live one: it shows small, at the bottom — Another call waiting, who it is, and your current call is not affected. There is no Answer button, because picking up would drop the customer you are talking to and there is no hold. Send to voicemail now, or do nothing and it rolls there by itself.
A second call coming in used to grab the controls — the customer you were talking to suddenly could not hear you.
The person you are talking to deserves to keep hearing you; the one waiting deserves voicemail rather than a dropped line. Knowing that nothing can cut a customer off mid-sentence lets a rep relax into the call — and relaxed reps sell better.
Press 2 for the parts department without reaching for your own phone
The keypad dials any number, and while you are on a call the same keys send touch tones — so supplier menus, inspection lines and county offices all work from inside the product. Type a number belonging to someone you have saved and their name appears under it. The number the customer will see is printed at the bottom, so there is no guessing which line is presenting.
The building department answers with a menu and the parts desk wants extension four, and neither can be reached without hanging up and redialling on your own phone.
Once a business runs more than one line — a sales number, a service number, an old one still lettered on the truck — the only one that matters is the one that rings back, so the presenting number sits under the Call button where it cannot be missed. It is normalised to a full country-code number before it ever reaches the carrier, because a line saved as ten bare digits is rejected at dial time rather than at the moment somebody typed it.
Call, text and email leave from the same box
Call sits beside SMS and Email above the reply box, on the same customer — because ringing somebody back is the third way to reach them, not a different piece of software. Text and email leave from that same box, and it is written up on the one conversation.
You finish reading a two-week thread, decide to ring him, and lose the thought hunting for his number in a dialer that opened on somebody else.
Reading a thread and listening to a recording is exactly when a person decides to ring back, and the old answer was to leave, open the dialer and re-find the man you were already looking at. When Call is greyed out it says which reason — this contact has no number, or the browser phone has not registered yet — because a dead button with no explanation gets reported as broken software.
Call from the card you were already looking at
The Call button on a new lead card on the board stages the number and dials it. The stage moves when the call actually connects — stamped by the carrier, not by somebody clicking a button that says they tried.
The board says nine leads were contacted this week, and four of those are somebody tidying cards on a Friday afternoon.
Marking contact by hand records the calls people remembered to log, which is never the same set as the calls that happened. Where a builder has no in-app phone at all, the manual log stays and dragging still works — nothing on our side can observe a call made on a personal handset, and pretending otherwise would be worse than admitting it.
A number nobody saved gets a name before you forget who it was
The phone searches your own contacts by name or by digits and dials from the row. Ring a number that is not in the book and it asks who that was — a name and the number, nothing else. The rest of the file gets filled in later by whoever has the time.
Recents is a column of ten-digit numbers, and the one that mattered — the man who wanted a 30x40 with a lean-to — is indistinguishable from the four robocalls around it.
The prompt is deliberately two fields. An intake form at the end of a call is the thing people cancel, and the trade-off is a thin contact — which is still worth far more a month later than a bare ten digits nobody can place.
You hang up and the write-up is already done
Direction, duration, which line it went out on, who took it and whether it recorded — taken off the call itself, not typed in afterwards by somebody who is already late for a site visit. When you hang up, the entry drops into the one thread on that customer's record and sits in order with the texts and the emails, voicemail included.
Somebody else picks the job up on Monday and has to ring the customer to ask what was agreed on Friday, because nothing on the record says.
The sentence and the facts are kept in two different places on purpose: the thread carries what a human reads, and a separate call table carries what you can count. One row trying to be both is how a business ends up unable to answer how many calls it missed last week.
A call nobody answered is still a fact
Rang out, busy, went to a personal voicemail, left a message, nobody was set to ring — each is written as its own cause, not as a blank. Once a call is known missed, a later 'completed' cannot flip it back to answered.
The record says the lead was contacted, so nobody rings back, and the message describing a 40x64 sits in a mailbox on a phone that man replaced last year.
A forwarded leg answered by somebody's carrier voicemail comes back from the carrier as completed, so the record cheerfully reported success while a lead sat in a personal mailbox nobody checks. The outcome is therefore monotonic — a definite signal is never overwritten by a late ambiguous one. Which cells and which signed-in screens get rung in the first place, how long they ring before the call gives up, and what happens when nobody picks up is all set per line on what happens when someone calls your number.
A recorded conversation is not a voicemail
Voicemail is calls nobody picked up — audio with no talk time against it. A recorded conversation stays on its own row in Recents, where the call is. And the audio is never a public link: it streams back through us, checked against the company that received it.
You go looking for the message the customer left about the door header and find it buried among forty recorded conversations that were never messages at all.
The voicemail list originally keyed off 'has a recording', which was correct right up until answered calls started recording too — at which point every recorded conversation filed itself under Voicemail. A voicemail is defined by nobody answering, not by a file existing.
The phone opens on the people you owe a call
One list, from two sources that mean the same thing standing in a driveway: calls somebody deliberately added, and missed calls nobody has rung back yet. The count rides on the puck, so the debt is visible without opening anything — and the full list is the same rows.
Friday's three missed calls are still unreturned on Monday, and the only place they ever existed was a red dot somebody cleared while looking for something else.
A queue built only from what people remembered to write down would quietly miss the expensive half, so open missed-call episodes are merged in on their own. Where both exist for the same number the human's entry wins, because it is the one carrying a note about what the call is for.
The call you owe is a task, not a note inside a widget
A queued call is an ordinary task row — urgency, a note saying what it is about, a due date, the contact it belongs to. So it appears on your list with the rest of the day's work, and it can be handed to somebody else with the reason attached rather than as a bare number.
The one man who took the call is off sick, and the three people covering for him have no idea anybody was promised a ring back.
A private list living inside a phone widget is where work goes to rot: nobody else can see it, it has no due date, and it dies with the browser tab. Making it a real task gives up a tidy separate table and buys reassignment, snoozing and shared visibility without writing any of them twice.
Or have it ring your own handset and bridge the customer to you
An outbound call can ring your cell first and connect the customer when you answer — your phone's audio, Bluetooth through the truck, and it still works on bad service at a site. No press-1 screening, because a keypress is four interactions with a glove on. The customer still sees the business number, not your personal one, and the call is still recorded against them — so a call back comes home where the whole team can see it.
Standing in a framed shell on one bar of service, with a laptop microphone that sounds like a wind tunnel, the call you needed to make simply does not get made.
The handset a builder already owns is better at being a phone than any browser will ever be, so this runs alongside the browser phone rather than replacing it — picked at the moment you press Call, depending on whether you are at a desk or on a roof. It needs your own mobile on file, and says so by name if it is missing. Same rule when the browser phone has not registered: the dock tells you it did not connect and offers to hand the number to this computer, instead of silently opening whatever dialer the machine has.
- 1Sign in and the phone is live. Nothing to install.
- 2Someone rings your line and it rings on your screen, wherever you are in the software.
- 3Dial out and the customer sees your business number, not yours.
- 4It stays connected all day — a long shift never drops the phone.
- 5Blocked microphone? It tells you what is wrong rather than pretending to dial.
- 6On a call: the call timer, Mute, Speaker, Note, Script, Task and End call — and Open conversation to text or email without hanging up
- 7A second call during a live one never takes it over: it shows small, at the bottom, and goes to voicemail
When the call happens in somebody else's dialer, the customer's file is not on screen at the moment they pick up, the outcome gets typed in later if at all, and the recording lives somewhere the builder cannot reach. The bar was set by what builders actually complain about in other dialers: no mute or speaker until the other person answers, no sound when they hang up, a mute button that does not mute, and calls that cannot be ended at all. So the phone lives here, and the record is on screen while you talk.
- Calls invisible to the business because they happened on a personal handset
- Dialer bugs that lose calls or lie about mute state
- No customer context at the moment of connection
A phone that floats over whatever you're doing
The phone is a dock, not a page. Full size gives you five tabs — Recents, Contacts, Keypad, Voicemail, Queue. Compact is the on-a-call bar. Dot is a single puck that pulses while a call is live. Drag it anywhere, drop it on the sidebar to make it a menu row, or park it top right. On a phone screen it stops floating altogether.
Mute and hang up that actually work
The buttons you use during a call. Mute, with the state read back from the call itself and a clear muted label. A running timer. And a hang up that always ends it, with a brief 'ended' state so you can see when the other end dropped. The buttons are there the moment a call exists — not only once somebody answers.
Keypad, and touch tones during a call
A big number box and a twelve-key pad. While a call is live, the same keys send touch tones, and the box says so. Type a number belonging to someone you have saved and their name appears. The number the customer will see is printed underneath.
Recent calls, searchable, with the reason each one was missed
Recents shows the facts, not the chat: who, when, how long, and — when it was missed — why. "It rang through to a personal voicemail." "No one was set to ring." "No answer." "Busy." A recording plays right on its row. Tap the name to jump to their estimate or their card.
Your voicemail box
Every voicemail, with what they said written out above the player. Switch between Everyone and For me. Search by name or number. Jump straight into that customer's conversation from any message.
Save the number you just called
When a number matches nobody, the phone asks one question: who is it? Type a name and you have a contact with the name and the number. Nothing else is asked. Next time they ring, you see who it is.
Told when the browser can't place the call
A plain notice above the tabs: can't call this number from the browser, here is the actual reason, and two buttons — call from this computer, or cancel. The handoff only happens if you choose it.
Dial out as your own number, all day
Every signed-in browser gets its own calling identity for your business. It is issued on the account that actually owns the number you dial out on, so your own line presents correctly. It renews itself before it expires, so the phone does not drop out mid-shift.
Ring my cell first, then connect the customer
Your own phone is the calling device. Bluetooth through the truck, lock-screen answer, works on bad rural signal. The customer still sees your business number, and the call is still written to their record. It sits alongside the browser phone rather than replacing it.
Your phone numbers, and who holds each one
One table: the number, what it is for, who holds it, how calls behave, its settings. Hand a line to a rep so each customer keeps talking to the same person and replies come back to them. A number you give up is kept, not deleted — so a reply to a message you sent last month still lands.

