OS-06 · systems · owned by Steve · portal

portal.

What the portal does with the information that passes through it. One section per area, written as each is built, so this stays the answer to “what does the portal do with this?” rather than a record of how things used to work.

last reviewedNov 2026
version1.1
statuslive · rest in progress
01

the short version.

read this first

The portal is where Zeal works: your day, our projects, the warehouse, our people and our money, in one place. It’s also where the OS and the playbooks live, and where you tell us what’s broken or what would help.

02

what’s in it.

the menu
01
home and your PA
Your day, what needs you, and your PA’s briefs.
02
projects and the planner
Every project from enquiry to debrief: quotes, plan, crew, documents and money.
03
warehouse and operations
The schedule, your shifts, stillages, labels, racks, vehicles and RAMS.
04
contacts
People, organisations and the directory.
05
finance
Invoicing, bills, POs, cash flow and the finance hub.
06
how we work
The OS, the playbooks, company info, privacy and what’s new.
07
bugs and ideas
What’s been raised, and what’s being fixed.
03

you see what’s yours.

The menu shows what your role opens, and nothing else. If something you need isn’t there, ask your manager.

04

what it connects to.

5 systems
01
currentRMS
For kit and quotes.
02
xero
For the accounts.
03
microsoft 365
For Teams and Outlook calendars.
04
dropbox
For files.
05
capital on tap
For cards.
05

people, organisations and money.

Who we bill and who bills us (people, organisations and legal entities, and how a bill or a PO finds the right job) is explained in the Finance playbook. Read who we bill, and who bills us →

06

something wrong, or an idea?

Press the thought bubble at the top of any page.

07

intake: the short version.

read this one

Every form on wearezeal.co lands in one place in the portal, called Intake. Each arrival notifies the shared mailbox it belongs to and carries a clock, so nothing sits unanswered. You still reply from the mailbox exactly as you do today. The portal’s job is to make sure nothing is lost, and to record what came of it.

Typeform and Zapier have been retired. Mailchimp still sends the catalogue and the newsletter, and that has not changed.

08

what arrives.

five forms

Each form notifies a shared mailbox as well as appearing in the portal, so there are two ways to notice an enquiry and one place to deal with it.

01
send us a note

notifies hello@

New business, general questions, anything that does not fit elsewhere. Two working day clock.

02
get the full kit list

notifies hire@

Somebody wants the rental catalogue. They receive it automatically, and it is a dry hire lead. Seven day clock.

03
used equipment

notifies hire@

An enquiry about a specific item we are selling. No clock, because there is no promise to keep.

04
careers

notifies careers@

Somebody asking about working here, in any capacity. No clock, but it is still a person putting themselves forward.

05
stay up to date

notifies nobody

A newsletter sign-up. Nothing to action. It lands closed and exists as our own record of consent.

09

how it flows.

automatic

From somebody pressing send to it sitting in front of you. Everything on this path happens without anyone intervening. Everything after it is deliberately a person’s job.

somebody presses send
A form on wearezeal.co. Nothing is stored yet.
the checks run first
A bot check before anything is written down, so most spam never reaches us at all, plus a rate limit so the forms cannot be flooded from one place.
recorded, with a clock
Status new, and for enquiries and catalogue requests a follow-up date. This is the point of no return: from here it exists and cannot be quietly lost.
the mailbox is told
An email from portal@wearezeal.co to hello@, hire@ or careers@, carrying a link straight to the record.
mailchimp does its part
Catalogue requests trigger the brochure. Newsletter sign-ups join the list. Only ever where somebody asked for it.
anything that failed is flagged
If the notification or the Mailchimp step did not work, it appears on the delivery problems tile rather than disappearing quietly.
a person picks it up
Claim, reply from the mailbox, record the outcome. Nothing is ever promoted automatically. A human decides every time.
the clock stops
It became a project, or it was closed. Either way it is off the follow-ups list and out of the digest.
10

what you do with one.

three steps

Claim it first. One click. It stops two people replying to the same enquiry, and it moves the follow-up reminder from the room to you.

Reply from the shared mailbox, exactly as you would today. The portal does not send email to customers and is not going to.

Then record what happened. Turn it into a project, add the person as a contact, create the organisation, or simply close it. Whichever fits.

! conversations in the mailbox, outcomes in the portal

If we ever start trying to hold the conversation inside the portal, we will have built a worse email client. Reply where you always have, then tell the portal what came of it.

11

the follow-up clock.

hello@ · hire@

Two of the five types carry a deadline. It is not a promise made to the customer, it is a nudge to us. Enquiries are due in two working days, catalogue requests in seven calendar days. The other three carry no clock.

Anything overdue appears in the Follow-ups view and in the daily digest. If nobody has claimed it the reminder goes to the shared mailbox; if you have claimed it, it comes to you.

The clock stops when an enquiry becomes a project, or when it is closed. It keeps running if you only add a contact or create an organisation, because recording who somebody is is not the same as answering them.

12

statuses.

five

An enquiry is new until somebody touches it. That is the default view, sorted oldest first, on the basis that the oldest untouched enquiry is the one most likely to embarrass us.

It becomes open once claimed, and ends as either converted, meaning it became a project and is tracked there, or closed, meaning it was dealt with and nothing needed creating.

Spam is marked rather than deleted, so we can see whether the bot check is doing its job.

13

quick reference.

if / then
a brochure did not arrive
→
Check the delivery problems tile. Send the PDF by hand, then close the loop.
two of you are replying at once
→
Claim before you reply. That is what claiming is for.
it is clearly spam
→
Mark it spam, do not delete it. We want to know how well the bot check is working.
it should be a project
→
Create project from the record. You get the full project form, and the ZPID mints on create.
the same person keeps coming back
→
There is a marker on the row when an address has been in before, so nobody gets chased twice in a fortnight.
something looks wrong
→
For a specific enquiry, whoever owns that mailbox. For how Intake behaves, Steve.
14

frequently asked.

detail
01
can everyone see everything, careers included?visibility
all staff

Yes. All staff can see all of Intake, applications included.

A deliberate choice rather than an oversight, on the grounds that a careers enquiry is not confidential and hiding it makes it easier to drop. If it ever needs to change, it is a settings change rather than a rebuild.

02
what exactly do we store about consent?marketing
hire@

The exact wording somebody was shown, their answer, and the moment they gave it.

Not a paraphrase of the wording, the wording itself, read off the page as it was rendered. If anyone asks what they agreed to, we can tell them precisely rather than approximately.

The timestamp comes from the database rather than the browser, and only where consent was actually given. A declined consent carries no timestamp, because there is no moment at which consent was given.

03
does the portal email customers?never
by design

No, and it is not going to.

It emails us, to say something has arrived. Mailchimp sends the catalogue and the newsletter because somebody asked for those. Every reply to a person comes from a human, in the mailbox.

04
can it promote something on its own?automation
no

Nothing is ever promoted automatically. A person decides every time.

No enquiry becomes a project, a contact or an organisation without somebody choosing to make it one. The automatic part ends the moment the record exists and the mailbox has been told.

05
what happens to attachments and CVs?uploads
careers@

There are none. No form on the site accepts a file, deliberately.

A public upload path is a standing risk for very little gain, so the careers form asks what somebody does and invites them to write. If we want portfolios later, that will be a considered decision rather than a default.