Joining a phone system to business software looks like a small integration and is not. Call detail records arrive with fields that do not mean what they appear to mean, recordings raise consent obligations that vary by jurisdiction, messaging providers differ in how they sign webhooks and how they deliver media, and number porting is a project of its own. The demo always works. Attribution at scale is where it goes wrong.
What the work involves
- Call records mapped to people and customers correctly, having verified which field actually carries what
- Recording storage, retention and consent handling designed against the jurisdictions you operate in
- Messaging in both directions, with signature verification on inbound webhooks
- Presence and click-to-call in the interfaces your team already uses
- Graceful behaviour when the provider is down, which it will be
- Number provisioning and porting planned as a lead-time item, because it always is
Why we are credible at this
We operate SIP infrastructure carrying live calls — Asterisk, Kamailio, FreeSWITCH and FreePBX — and we know from production that a configuration write without an explicit reload never reaches the running switch, and that the caller-ID field on a call record carries the trunk rather than the extension.
What moves the price
We quote after discovery and the number is fixed before anything starts. These are the things that move it, so you can see roughly where your project sits before you talk to us.
- Which provider or switch you are on, and how much of its behaviour is documented
- Whether recordings are involved, which brings consent and retention into scope
- The number of jurisdictions you operate across
- Whether numbers need porting, which is a schedule risk more than a cost
Questions we get asked
Other App Development work
Tell us what you are trying to do
A short conversation is usually enough to tell whether we are the right people. If we are not, we will say so and point you somewhere better.