Solutions / Customer operations

Requests completethe first time they arrive.

Change of holder, readings, corrections: the days are lost going back and forth for one missing detail. Synapsi checks each request on arrival and asks for exactly what is missing.

Billing, meter and account serviceillustrative
Change of holder · request check
CUPSpresent
New holder's NIFpresent
IBANmissing
Sent to the account deskwaiting
Complete on arrival, or asked for the one thing missing.
Where the value comes from

Nothing left on the table.

01
Hours back

No more chasing one field

Requests are checked the moment they arrive, and the customer is asked for exactly what is missing.

02
Money in

A request that completes is a contract that starts

A change of holder that is not stuck in a queue is supply you are billing sooner.

03
Risk avoided

Replies with a source

Drafts are grounded in your own documents and reviewed by a person before they are sent.

Workflows that apply

Start from templates built for this work.

wf-052

Change of holder, missing data

Checks the CUPS, the new holder's NIF and the IBAN on arrival. Incomplete requests go back naming the one thing missing.

wf-060

Hydrate from CRM

Looks the customer up by CUPS, contract or phone first, so every later step has the real record.

wf-031

Meter reading to sheet

Appends a submitted reading to your readings spreadsheet, then confirms it to the customer.

wf-037

Inbound email, drafted for review

Searches the Company Brain, drafts a reply grounded in what it found, and posts it for a person to send.

wf-048

Regularisation explained

Explains a catch-up invoice before they phone, with the kWh and the difference exactly as your system produced them.

wf-038

New customer onboarding

Creates the customer in the CRM, gives them a documents folder, then welcomes them, in that order.

Using a template creates a draft. Publishing it is a separate, deliberate step.

Before and after

A change of holder arrives with no IBAN.

Today
  1. A change of holder arrives with a CUPS and no IBAN
  2. It waits in a shared inbox
  3. Somebody notices three days later and writes back
  4. The customer replies, and the request starts again
With Synapsi
  1. The request arrives and the customer is found by CUPS
  2. The three required details are checked at once
  3. The customer is asked for the IBAN, by name, the same minute
  4. The complete request reaches the desk, ready to file

Illustrative run. What actually happens depends on the systems you connect and the permissions you set.

What it takes

Your systems, your rules, your skills.

Skills the agents use
move-home-change-of-tenancytake-a-meter-readingverify-who-you-are-speaking-to
What you connect
  • A CRM keyed on CUPS, contract or phone
  • A connected inbox
  • Your readings spreadsheet
  • A channel for the account desk
Works with the software you already run
GmailOutlookGoogle SheetsHubSpotSalesforceSlack
BoundarySynapsi prepares and routes the request. Filing it with the distributor stays with your desk.

See it on your own process. Not on a slide.

Tell us how customer operations work runs today, and we will show you the first workflow to put into production.