Appearance
Client pipeline: from QR scan to Client Admin
flowchart LR
A[QR / NFC / link] --> B[Form submitted] --> C[Call booked]
C --> D[Research brief generated] --> E[Call done] --> F[Quote sent] --> G[Contract signed]
G --> H[Paid via Stripe] --> I[Owner marks Lead converted] --> J[Client Admin account issued]
First contact: QR codes, NFC and links
- Every business a salesperson (or the owner) adds gets a unique link, shown as a QR code, copyable link, and NFC-writable URL. The link records which salesperson and which business the lead came from.
- Scans are logged (time, salesperson, business) for the sales metrics.
The public form
- Short, dynamic, front-facing. Built as a multi-step form (beUI Adaptive Stepper). Questions adapt to earlier answers (business type changes later questions). Prefilled with the business name when the link carries one.
- Asks for: name, business, role, email, phone, what they want, social handles, preferred call slot.
- Shows a privacy notice and requires consent (UK data protection).
- Call slot picker reads the owner's real availability from the global calendar (booking hours from Settings minus existing events).
DECIDE 1: login at the form?
Default: no login at all for the form. A Google button is not shown here. Google is not used as a client sign-in method; client accounts are only created after payment. Setting: calls.formRequiresLogin.
On submit
- Lead created, credited to the salesperson on the link.
- Discovery-call event created on the owner's calendar (and the salesperson's, scope
own_sales). - Lead shown on the management screen and on the salesperson's planner.
- Email to the lead: "Your call has been booked" with date, time and how the call will happen.
- Research job enqueued (Leads and research).
DECIDE 2: booked or approved?
The user asked for "approved". If calls need manual approval first, the email becomes "requested" and a second "confirmed" email goes on approval. Default: booked instantly, confirmed email straight away. Setting: calls.bookingMode.
Call
- Owner (or salesperson) opens the lead page: form answers, research brief, call notes, outcome.
- A lead who submitted but did not book a slot is flagged for in-person follow-up after N days (setting
leads.followUpAfterDays, provisional).
Quotes, contracts and payment
- Quote is sent by email with a link to a public quote page. Statuses: draft, sent, viewed, accepted, declined, expired.
- Contract is generated from a template, editable before sending, sent only after the owner explicitly approves it. The system refuses to send a contract with unfilled
. Signing records name, IP, time and a hash of the signed text. - Payment link comes from Stripe and is included with the contract/acceptance email. Stripe's webhook marks the lead Paid. A manual "record payment" runs the same path.
- Versioning rule (important): quote, contract and price templates are versioned. Editing a price or template creates a new version that applies to future quotes and contracts only. Every sent quote and signed contract stores a frozen snapshot of its terms. Example: a client signs 4 months at £1,000; the owner then changes the price to £1,200; the signed client stays on £1,000 for that contract, and only new contracts use £1,200. Mechanics: Versioning.
Lead conversion and the Client Admin account
The brief described two triggers (payment done, and owner marks "Lead converted"). This plan joins them:
- Stripe payment confirmed → lead status Paid, awaiting conversion → appears in the owner's "Needs you" list.
- Owner clicks Mark as converted. Confirm step shows the proposed username prefix for the business (suggested from the business name, e.g.
dessertshop), editable once, never changed afterwards. The Client Admin username is<prefix>-admin. - System creates the organization (client business), the Client Admin user, the plan, and default event types/schedules.
- Credentials:
- The username is generated; the password is a random, high-entropy temporary password (e.g. 20 characters from an unambiguous alphabet), stored only as a hash and flagged must change at first sign-in.
- Delivery, default: the client is emailed the username and a single-use set-password link (expires in 24 h, setting
access.setPasswordLinkTtlHours). This is more secure than emailing a password. - Owner copy: the owner also sees the username and temporary password once on screen so he can pass it on directly if the email fails.
- First sign-in forces a new password (minimum 12 characters), then TOTP set-up for the Client Admin, then a "Your details" screen (confirmed email, phone).
DECIDE 3: who sends the credentials?
Whether the owner sends them himself or the system does automatically. Default: system sends the link, owner can copy the one-time password as backup. Setting: access.credentialDelivery.
Sub-accounts
- Client Admin requests a sub-account from their dashboard (name, email, role: salesperson, editor, social media manager, other).
- Request lands in the owner's "Needs you" list. Owner approves → system creates the Client Member and emails them a username and set-password link. Owner can decline with a reason.
- Client Admin can disable a sub-account at any time; re-enabling needs owner approval.
Ending
Marking a client ended removes crew assignments, cancels future events, disables all the business's logins and stops reminders. Paused holds everything without removing anything.