Customer service walkthrough · October 2026

Routine answers on every channel. A person when it matters.

A short walkthrough of how Provident residents could get quick answers by phone, in the portal and from the website, while your billing team gets the full context for the requests that need a person.

30%Target: reduce calls by thirty per cent, so the service team can grow without adding headcount at the same pace.

Watch the walkthrough See the scenarios

The walkthrough

About six and a half minutes. Pick a chapter to jump straight to it. Captions are off by default and available from the player controls.

Sample data throughout. The phone call is a simulated recording; the assistant's replies are real. The inbox views show the emails that were actually delivered.

What you will see

Six everyday situations, from a quick balance question to a request that needs your billing team, and how a manager would track it.

A resident calls

Jonah calls the billing line. The assistant confirms his account by phone and gives him his balance and due date, with no representative needed.

See it at 0:43

Answers in the portal

Priya logs in and sees her balance, due date and payment status. In the chat she asks how sub-metering works, picks one of her two units, gets her September bill compared with August, and enrols in pre-authorized payments, with an email confirmation.

See it at 1:46

Moving out

Jonah tells the assistant his move-out date. It already knows his unit, explains the notice rule, and once he confirms, the request is captured in Salesforce as a structured record, with nothing to re-key. A confirmation email follows.

See it at 3:09

No login needed

From the Provident website, Priya clicks Contact us, enters her account number and postal code, and asks for her balance and due date. The answer arrives by email, checked against her account.

See it at 3:55

When a person is needed

Devon asks for a payment arrangement and adds a complaint. Each goes to the billing team with a summary and a request number, and a billing representative takes ownership without asking Devon to repeat himself.

See it at 4:30

The manager's view

In Salesforce, the service dashboard shows case deflection against the 30% target and the share of requests by type and channel, as percentages. Every chart opens its report, so the team can see what to automate next.

See it at 5:38

Next steps

A practical way to move from this walkthrough to a plan for Provident.

Working sessionWalk through the scenarios with your service and billing leads and note what fits.
Pick the starting pointChoose the request types and channels that would make the biggest difference first.
Agree how to measure itA pilot would measure progress toward the 30% target against real Provident contact volumes, starting with balances, bills, payments and moves. How your billing system (Cogsdale) and phone system would connect is confirmed during discovery.