Modules › Contacts and follow-ups

module · not built yet

Every customer, on one timeline

Every enquiry, order, booking and chat should land on a single record for that customer, so you see the whole relationship at a glance instead of hunting through three inboxes. Tags, and follow-up reminders your Manager actually sends. The useful part of a CRM, without the CRM project nobody finishes.

Not built yet·this page describes what we intend to build, not something you can turn on

what it would be

The whole relationship, in one place

One timeline per customer

The web enquiry, the phone call, the order, the booking and the chat would all attach to the same person. Open a contact and the whole history is there in order, not scattered across tools that do not talk to each other.

Tags that mean something to you

Group people the way your business actually thinks: past customers, quote sent, VIP, needs a call back. Simple labels, yours to define, so a list you need is a filter away.

Follow-ups that get sent

Ask your Manager to remind you, or to reach out for you, and it happens. The follow-up that keeps slipping because everyone is busy is the one this would quietly take off your plate.

Grown from data you already have

It would not be a second system you copy people into. Your enquiries, orders and bookings already live in your site's own database; this is that same data surfaced as people. Nothing to import, nothing to keep in sync.

how it would run day to day

Ask, and it follows up

You would not maintain it. As enquiries and orders come in, the timeline builds itself. When you want something followed up, you tell your Manager in plain English: "remind me to call Sarah on Thursday", "tag everyone who asked about weddings this month", "send last winter's customers a note about the new service".

Anything going out to a customer would arrive to you as a preview first, the same gate every other change goes through, so a follow-up is never sent in your name without you seeing it.

Your data already lives in your site's own database, and contacts would live there too. Yours to export any day, and if you ever leave, it leaves with you.

a sketch, not a screenshot

Sarah Nguyen customer

  • enquiry · garden room, Feb
  • booking · confirmed
  • order · mixed dozen
  • follow-up · call Thursday
what it would cover

In plain scope

Every line below is intent, not inventory. None of it is running for anyone today.

  • One timeline per person across every enquiry, order, booking and chat
  • Tags you define, to group people the way your business thinks
  • Follow-up reminders that actually get sent, through your Manager
  • Your contacts in your own database, yours to export any day
what we leave out, and why

And what it is not

Knowing the edges up front is the point. Here is what this module deliberately does not do.

Not a sales prospecting CRM

This is your customers' memory, not a prospecting machine. Deal-stage pipelines, lead scoring and cold-email sequences are a different tool for a different job, and loading them here would turn a clean customer record into a sales CRM nobody asked for.

No data enrichment or scraping

We do not buy, scrape or append data about your customers from the web. What sits on a contact is what they gave you or did with you. Consent-first is the whole point, and it keeps you on the right side of privacy law.

honestly
not built yet

Nothing on this page is switched on

Where this actually is today: nowhere. There is no contact record, no timeline, no tags and no reminders. Not in a beta, not behind a flag, not on one site. This page exists because the idea is on our roadmap and we would rather describe it in the open than keep a plan in a drawer, but it would be a straightforward lie to call it a module you can add.

What is true is the ground it would be built on. Your site already keeps its enquiries in its own database, and the bookings, store and membership work writes to the same place, so contacts would be that data surfaced as people rather than a second system you copy anyone into. That makes it a smaller build than a CRM project. It does not make it a built one.

If this is the thing you actually want, say so. Knowing which module people ask for is how we decide what gets built next, and being the business that asks first gets you an honest conversation about timing rather than a date we invented to close you.

Tired of the customer history living in three inboxes?

Tell us how enquiries reach you today. We cannot sell you this one yet, but knowing you want it is what moves it up the list, and there may be a simpler thing we can do for you in the meantime.

Tell us you want contacts