Skip to main content
agent — identity
knowledge
ability
connected app
approval
tests — passing
001 — agentic customer journeys — aotearoa new zealand

Agentic customerjourneys, assembledone agent at a time.

Specialist agents sit inside your business, read the signals your systems already hold, and prepare the next thing for every customer — the first quote through to the tenth year. Each one drafts. A person approves.

live · reads one page · about ten seconds
Watch one assemble itself out of your business.

Paste your web address. It reads one page, builds a specialist that knows what you sell and how you talk, takes on your own colours, and shows you the questions your site leaves hanging. Then ask it something — it answers from your business, and tells you plainly when your site never said.

One public page, about ten seconds. Nothing is stored and nothing is sent.
business blueprint · living source · connected
01 — Business Blueprint

They work from
your rules, not theirs.

What you sell. What you charge. What you would never agree to without checking first. Written down once, in one place, and every agent reads it before it does anything.

Change the spend limit here and every agent uses the new number from that moment. This is the part that makes it sound like you.

Your business, written down in use
01
What you sell
your list
What you charge for it
your prices
03
How you talk to people
your words
04
What you’d never agree to
your rules
Who has to sign it off
your people
journey composer · assembled · traced
02 — Journey Composer

A customer isn’t
an enquiry.
They’re twenty years.

The first quote. The job itself. The follow-up nobody got round to. The warranty that ran out quietly. The call they made to somebody else three years later, because you had gone quiet.

Every one of those moments is already recorded somewhere in your business. They just sit in different places and never reach anyone in time to matter.

assembl joins them up and prepares the next one, so the relationship stops depending on whoever happens to remember.

The five steps running
Someone asks
“can you do this?”
02
Work out what they mean
reads the request
03
Check a couple of things
your prices · your rules
Write it up
draft ready
05
You say yes
then it goes
intent · history · what you offer
03 — Who’s asking

It reads what
already happened.

Someone who has ordered the same thing every Friday for a year should not be asked what they like. Someone who has never dealt with you before should be asked properly, and asked well.

Every agent reads the whole history before it says anything — what they bought, what went wrong once, what they were promised. Usually there is one question left to ask.

“Can you do Thursday?” two people
A
Dealt with them nine times
asks nothing
“Thursday works — same as last time, and I’ve put you down for the morning.”
First time here
asks three things
“Happy to. Whereabouts are you, what’s the job, and does morning or afternoon suit?”
agent harness · specialists · contracts
04 — Agent Harness

Specialist team members,
not one that does everything.

One watches for work coming due. One watches what is about to lapse. One notices a customer who has gone quiet. One drafts the message and one checks it against your rules before you ever see it.

Each has a single job, a written list of what it may touch, and an authority level that says how far it can go on its own. Nothing that commits money or reaches a customer gets past “draft” without a named person.

assemble an agent →
Build one click a part
0of six

Six parts. Place them and watch what you get — each one does a single job.

How far each one may go authority
Observe
watches, says nothing
02
Draft
writes it, holds it
03
Recommend
puts options to you
Act with approval
your click, then it goes
05
Anything with a cost
never past draft alone
the wait · a credit · one question back
05 — Assembling · The Wait

A fair trade
for the wait.

While an agent works, your customer watches it happen and earns a credit toward what they’re buying. In return it asks one optional question — how they’ll use it, when suits, who else it’s for.

By the time the work is ready you know something about them you didn’t, and they have something back for the wait. Neither of you spent anything extra.

One line of code to add.

While you wait both getting something
Reading what they asked for
+ credit
“Anything we should know about the site?”
optional
Checking it against your prices
+ credit
“Does morning or afternoon suit?”
optional
Putting the draft in front of you
credit banked
assembling — 0%
proof · evidence · measured
06 — Assembl Proof

A flight log,
not a dashboard.

Every job finishes with a record you can actually read. What each specialist looked at, what it wrote, who approved it, and how long the same job used to take you before.

Measured numbers and calculated ones are kept apart, and labelled. If we worked something out rather than counted it, the log says so.

Flight log — this job certified
01
What each one read
every source, in order
What it wrote
the draft, kept
03
Who approved it
named, and when
04
Time taken
measured
Time saved
calculated · labelled
live demo · a real agent · drafting
07 — Live Demo

Ask it
something.

A real agent, answering from a sample business. It writes drafts. It doesn’t send them.

Agent — live ready
47min
returned per journey
94%
customer satisfaction
55%
wait revenue — yours

Build intelligence
you can understand.