Why we built reliability first
Every call and text you make through Pipedrive turns into an activity on a contact. That sounds like a small feature. It isn't. Underneath it is a question we spent a lot of design time on before writing the product features people actually see: what happens when something goes wrong halfway through?
A call is not finished until the record is useful
A completed call should become a useful CRM activity, including the context your team expects. Temporary service interruptions should delay that result, not quietly erase it. Totally Called keeps track of work that still needs to reach Pipedrive and resumes it safely when the connection is healthy again.
That principle is deliberately visible in the product: activities show their logging state, connection problems have a clear recovery path, and retries do not create a pile of duplicate records.
Order isn't guaranteed, so we don't rely on it
Calls move through ringing, in-progress and completed states. Network conditions can make those updates late or repeated, so the final customer-visible state matters more than arrival order. The result your team sees should stay accurate and appear once.
Failure should be loud, and recoverable, not silent
Services can be briefly unreachable and connections can expire. What matters is that a problem is visible, the product explains what needs attention, and pending work can recover after the connection is restored. Silent loss is not an acceptable product state.
How we check this actually holds
We test interruptions, delayed updates, repeated updates and reconnection before a change ships. The acceptance check is simple: the CRM ends up with one accurate activity for the communication, and the team can continue working without manual clean-up.
We're not publishing this as a benchmark or a number to hold us to — infrastructure evolves and so will the tests. What we can promise is the habit: reliability is treated as a first-class design constraint here, checked the same way correctness is, before a feature counts as done.
What this means for you
Practically: when you make or receive a call through Pipedrive, you shouldn't have to wonder whether it landed in the CRM. If it doesn't show up within a moment or two, our working assumption is that it's a bug we want to hear about — not an acceptable rate of loss we've priced in. That's a deliberate choice about where engineering time goes, and we thought it was worth explaining rather than leaving invisible.