3CX/We build and run it for you.

Know who's calling before you pick up.

Call logging and customer context, synced between 3CX and your ERP in real time. An inbound call is matched to the customer record so whoever answers already knows who it is, and the call ends up logged against the account rather than in someone's memory.

This is the smallest thing we sell, and the one that tends to change how the day feels on a trade counter.

Talk to us

You need a 3CX instance you can configure. We don't sell or host 3CX.

Docs

The integration documentation is public, so your IT team can review exactly what we call before you talk to us.

Open the 3CX docs

Why there's no screenshot on this page

The other products have a screen in the DataShift app, and you can see them on their own pages. This one doesn't. The whole integration lives inside the two systems you already have: the context appears in 3CX, and the call record ends up on the customer in NetSuite. There's nothing new for anyone to log into, and no dashboard for us to show you.

We'd rather say that than mock up a control panel that doesn't exist. If you want to see it working, we'll ring you and you can watch your own record open.

What's in it

Customer context

The caller is matched to the customer in your ERP, so the agent doesn't have to ask a returning customer for their account details again.

Call logging

Calls are written to the customer record as they happen, which means the next person can see that someone already rang about the short-shipped order.

Both directions

The sync runs both ways, so what 3CX knows and what your ERP knows don't drift apart over a quarter.

Anything beyond that

Ask, and we'll tell you whether it's built or whether it's work. This page deliberately doesn't list features we haven't shipped, which is why it's shorter than the other four.

Pricing

Scoped to your phone system.

The smallest thing we sell, and the number reflects it. We look at your phone data first.

3CX

Scoped to you

Quoted in writing before any work starts.

We check your phone data before quoting
One extension first, then the team
We don't sell or host 3CX

Book a walkthrough

No standard price list, because no two businesses look alike. You get one clear number, and you can walk away from it.

How a build goes

01
We check your phone data. This is the whole job. If half your customer numbers are formatted six different ways, matching fails and the integration feels broken.
02
One extension first. Usually whoever answers the most calls. Most teams see whether it's working within the first hour of use on that extension.
03
Then the rest of the team. The build is short. The number-cleaning is the part with the uncertain end date, and it's yours as much as ours.

docs.datashift.com.au

Read what we run before you agree to it.

The integration documentation is public, so your IT team can review exactly what we call before you talk to us.

All DataShift docs

We'll look at your phone data first.

How customer numbers are stored tells us how well matching will work, and that's the whole answer to whether this is worth doing.