Techbanq

Software · Salesforce integration

Salesforce is the front office; the truth it shows lives behind it

Sales and service act on what Salesforce shows them, but the facts that matter — whether the order shipped, whether the invoice is paid, whether a case is open — are owned by the ERP, finance and the service desk. Integrating Salesforce is making it reflect that back-office truth in near real time, without letting it quietly become a competing copy, and doing all of it inside the API and governor limits Salesforce meters every call against.

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Where it misleads

The four ways a disconnected Salesforce quietly misleads a revenue team

A Salesforce that is not properly integrated does not look broken; it looks confident and is often wrong. These are the specific ways it misleads the people who trust it most.

  1. 01

    A status that stopped being true

    The order shipped and the invoice cleared in the back office, but Salesforce still shows the state it held at the last manual update, so a rep reassures a customer about something that is no longer the case.

  2. 02

    A second customer master that drifts

    Details edited in Salesforce and never sent back, or copied in and never refreshed, turn it into a rival version of the customer that disagrees with the system that actually owns the record.

  3. 03

    A limit hit at the worst moment

    An integration that ignores API limits runs fine in testing and then, on a busy day at volume, exhausts the daily call allowance and stops updating — precisely when the data mattered most.

  4. 04

    Access that does not match the directory

    Salesforce logins managed separately from the company directory mean a leaver keeps access after their main account is closed, and joiners wait on a manual step the rest of the estate does automatically.

The core idea

Why Salesforce shows a customer who stopped being real weeks ago

Salesforce is a front-office system, and it is very good at that job: managing the relationship, the pipeline and the conversation. What it is not is the owner of most of the facts a customer conversation turns on. Whether an order shipped is the ERP’s truth; whether an invoice is paid is finance’s; whether a case is open is the service desk’s. When those systems are not integrated, Salesforce shows whatever was last typed into it, which is a snapshot that was accurate on the day it was entered and has been quietly ageing since. The screen looks authoritative, and it is describing a customer who has moved on.

The fix is not to make Salesforce own more; it is to make it reflect. Each fact keeps its owning system, and integration brings that fact into Salesforce in near real time so the front office sees the current state without becoming a competing copy of it. Where a fact genuinely originates in Salesforce — a call outcome, a next step, a relationship note — it flows back to whatever needs it. The discipline is naming one owner per fact and then keeping Salesforce honest against that owner, so the confident screen a rep relies on is confident because it is current, not merely because it is bold.

The shape of it

What feeds Salesforce, what it must not own, and where identity ties it to the estate

Salesforce sits at the front of the revenue estate, drawing facts from the systems that own them and returning the ones it originates. The boundary in the middle is where limits are respected and where identity connects it to everything else.

A surface diagram: ERP and order management, finance and billing, and the service desk feed into a single Salesforce integration boundary that respects API and governor limits and connects single sign-on, then produces a current customer view, returns Salesforce-originated facts to the back office, and keeps access aligned with the company directory.

  • ERP and order management

    Order and fulfilment status flows into Salesforce so a rep sees whether goods shipped, without Salesforce owning the transaction.

  • Finance and billing

    Invoice and payment state reaches Salesforce as a reflection, so a conversation about money rests on finance’s truth, not a guess.

  • Service desk

    Open cases and their status appear beside the account, so sales and service are looking at the same customer.

What we do

The Salesforce integration boundary

One place that respects API and governor limits — Bulk API for volume, Platform Events and Change Data Capture for near-real-time change — and where single sign-on ties Salesforce access to the company directory.

  • A current customer view

    Sales and service see the customer’s real state assembled from the owning systems, not a copy that aged since the last manual edit.

  • Facts returned to the back office

    What genuinely originates in Salesforce — a next step, a call outcome — flows back to the systems that need it, once and cleanly.

  • Access that follows the directory

    A joiner or leaver handled in the directory is reflected in Salesforce, so access never lingers after an account is closed.

Each fact keeps its owning system; Salesforce reflects them within its limits, and identity keeps it part of the estate rather than an island.

Our role

What we connect to Salesforce and what your revenue operations team keeps owning

  1. 01

    Integrations that fit the limits

    We design every flow against Salesforce’s API and governor limits from the start — Bulk API for volume, Platform Events and Change Data Capture for change — so it stays reliable on the busy day, not only in a quiet test.

  2. 02

    Reflection, not a second master

    We name the owning system for each customer fact and build Salesforce to reflect it in near real time, so the front office is current without turning into a rival copy that drifts from the back office.

  3. 03

    The Salesforce org stays yours

    How your objects, page layouts and automations are configured is your admin team’s domain; we integrate into that configuration and connect identity to your directory rather than managing your org for you.

Your Salesforce configuration and your commercial process are your team’s to own; we connect the back-office systems that hold the truth, keep every flow inside Salesforce’s limits, and tie access to your directory, so the front office reflects the customer’s real state without becoming a second version of it.

Common questions

What buyers ask

What happens when an integration hits Salesforce’s API limits?+

It stops making calls, which in practice means it stops updating, usually silently and usually on your busiest day. Salesforce meters API usage against a daily allowance and enforces per-transaction limits, and an integration that was built without counting them can pass every test at low volume and then fail exactly when traffic is highest. Designing for the limits from the start is the whole discipline: using the Bulk API for large loads rather than one call per record, using Platform Events or Change Data Capture to be notified of changes instead of polling constantly, and batching so a spike does not exhaust the allowance. An integration that respects the limits is not merely more efficient; it is the difference between one that works at volume and one that quietly falls over when it matters.

Should the customer master live in Salesforce or somewhere else?+

It depends on the fact, and the honest answer is rarely "all of it in Salesforce". Salesforce is the natural owner of relationship data — the contacts, the pipeline, the activity history the front office creates. It is a poor owner of the financial and fulfilment facts that live in the ERP and finance, because those systems are where those facts are created, validated and governed. The discipline is to name one owning system per fact: let Salesforce own what it genuinely originates, let the back office own the transactional truth, and integrate so Salesforce reflects the latter without holding a second, drifting copy. Making Salesforce the master of everything is how you get a confident front-office screen that disagrees with the system that actually ran the transaction.

How do you keep Salesforce in near real time without polling it constantly?+

By letting the systems announce their changes rather than asking them repeatedly whether anything changed. Constant polling — a job that calls Salesforce every few minutes to check for updates — is the quickest way to burn through the API allowance for very little benefit, because most of those calls find nothing new. Salesforce provides Platform Events and Change Data Capture precisely so a change publishes a notification the moment it happens, and the integration reacts to that instead of scanning. In the other direction, back-office changes are pushed into Salesforce as they occur. The result is near-real-time freshness that costs a call when something actually changed, not a call every few minutes whether or not it did.

Next step

Connect the front to the back

An integration design that fits Salesforce’s API and governor limits, names the back-office owner of each customer fact, and connects identity, before the first flow is built.