In your own inbox, on your own rules, while you’re doing something else. Chief reads each message, writes the reply the way you would have written it, and asks what you always need to know first. Approval stays yours on every send.
“Hi — is this still available? I’d love to come and see it this week.”
“It is. Before we take it any further — when are you looking to move, what budget are you working to, and what’s the best number to reach you on?”
Your words, your rules, your own account.
People enquire in several places at once and stop looking the moment somebody useful comes back to them. An answer in a minute gets the conversation. The same answer at nine the next morning gets read, and nothing else. Chief closes that gap on every enquiry, not just the ones you happened to be at your desk for.
It went to you and to three other people at the same moment.
Their question answered, and the things you always need to know asked back.
The next morning. By then they have been talking to you since last night.
One minute, not the next morning
Setup asks how you actually work: what you want out of an enquiry, who you’ll take and who you won’t, what you need to know before you’d give anyone a time, and a few of the replies you already send. That becomes your standing brief, and every reply is written against it. Anything the brief doesn’t cover, Chief doesn’t invent — it hands that one to you.
Qualify them properly before anything else happens.
Yes: working professionals, postgrads. Ask more: couples, short stays. No: smokers.
Phone, email, budget, move-in date.
“Hi — thanks for getting in touch…” Your greeting, your three standard answers, your sign-off.
Tell Chief how you work — your rules, your wording, the questions you always ask — and read your first drafted reply this afternoon.
Every rule you set is one of three things: fine, worth asking more about, or a no. Chief asks in the thread, checks what comes back against your rules, and collects what you always need before you’d offer anyone a time. The ones that can’t work are turned down in your own words, and you never have to read them.
Wants to bring a cat — asked, not decided.
Two months to begin with — flagged for you rather than answered.
Chief isn’t a service that posts for you from somewhere else. It answers in the account the enquiry arrived in, one conversation at a time, and how much it does without asking is a setting you own.
Every reply is written and sent in the account the enquiry arrived in — your name on it, the whole thread underneath it, and no third address anyone has to trust.
Chief answers a thread the way you would: reads it, writes the reply, moves on. Nothing is blasted at a list, and nothing is posted anywhere on your behalf.
Whether a reply waits for you to read it or goes out on the rules you gave it is your setting, and you can change which at any time.
Thirty minutes, your inbox and your rules — a real enquiry read, screened and answered in your words, live.
You don’t have to hand Chief one thread at a time. Start a pass over the inbox and it works down what’s waiting — read, reply, next — while you get on with something else. It’s a run you start rather than something ticking away in the background: it happens in the inbox you have open, you can stop it whenever you like, and a long queue can take more than one pass.
Nine enquiries came in after you shut the laptop on Friday. Nothing typed yet.
Chief works down them on your brief: your rules, your wording, your questions.
Each answered in the thread it arrived in, while you were making a coffee.
Nine replies before the first phone call
A good first reply is not what loses the lead. What loses it is the fortnight afterwards, when nobody remembered to go back. Chief keeps track of who never came back and sends the next message itself, on the same brief as the first one.
Their questions covered, and two viewing times offered.
Chief goes back to the thread — both times still free.
One more, offering something closer to what they asked for.
Replied on day nine, and back in play
That’s your setting. Every reply is drafted in the account the enquiry arrived in, and you choose whether each one waits for you to read it or goes out on the rules you gave it. Auto-send is off until you turn it on, you are told exactly what it permits before you do, and nothing is ever sent on a rule you didn’t set.
Nothing Chief does looks like a bot to the site you’re on. It works inside your own logged-in account, answers one conversation at a time at the pace a person answers, and only ever writes in threads somebody sent to you. It doesn’t post at a list, and it doesn’t repost or refresh anything to make you look busier than you are — which is the behaviour those rules exist to stop. We can’t speak for another company’s terms, but Chief is deliberately built to work the way you would.
Yes. Setup asks for a few of the replies you already send, and Chief writes against those: your greeting, your wording, your sign-off. It answers from the brief you gave it rather than from a generic script, so a reply reads like the one you would have typed. Anything the brief doesn’t cover it doesn’t invent — it says you’ll come back to them, and passes it to you.
Yes. Tell us what’s changed — a new dealbreaker, a question you want asked, a reply you’d rather it copied — and we update your brief for you. There is no rules screen for you to keep up to date, which is most people’s favourite part: you say it once, in your own words, and the next reply is written that way.
Yes, and that is how most people use it: start a pass and Chief works down what’s waiting, read, reply, next. It is a run you start in the inbox you have open rather than a service ticking away in the background, so you can watch it and stop it whenever you like, and a very long queue can take more than one pass.
Wherever the conversation continues in writing. Chief works on the threads in front of it, so it isn’t tied to one site or one inbox: listing enquiries, marketplace messages, WhatsApp, LinkedIn and Slack, and your own email are all threads it can read and answer, whichever webmail you use. Somewhere we haven’t met yet is configuration rather than code, so tell us where your enquiries land and we’ll add it.
No, and we would rather say so. Chief replies from your own machine and your own account, which is what keeps your name on every message. So the promise isn’t an inbox that empties overnight — it’s that nothing waits for you to find the time: the moment you’re at the machine, everything waiting is answered in minutes rather than over a morning.
Yes. Your data is encrypted in transit and at rest, your conversations are never used to train third-party models, and you choose what gets shared. Enterprise plans add further security controls and SSO.
Answer the questionnaire once and Chief has your brief. The next enquiry that lands gets the reply you would have typed, in the account it arrived in.