The Warm No: Declining a Prospect Without Losing the Relationship
Saying no to a website visitor is easy. Saying it so they leave thinking better of you is a craft: when the no is said, how it is worded, why the help continues, and six decline messages you can adapt.
TL;DR: Saying no to a website visitor is easy. Saying it so they leave thinking better of you is a craft, and most of it is decided before anyone types a word. This post looks at the decline from the visitor's side of the chat: when the no is said and why it waits, how a good decline message is built, why the visitor keeps getting real help after it, what happens when they push back, why the whole conversation is kept, and what your team hears about it. It ends with six decline messages for six industries, written as examples you can adapt.
Every business turns people away. The only question is how.
On most websites the answer is badly: a form nobody replies to, a meeting that ends ten minutes in with "we're probably not the right fit", a chatbot that says "sorry, I can't help with that". None of those is a decision, and the visitor feels it.
An inbound sales agent can tell during the conversation that someone is not a fit (if the idea is new, start with what an AI sales agent is). Once it can tell, it has to say something.
Deciding who gets a meeting is covered in How to Write a Door Policy for Your Sales Calendar, and the case for standards in We Built an AI That Says No. This post is narrower: the moment of the no, and the hour after it.
Where a no comes from
In Aijent, a visitor can be declined from two places, and the wording differs between them.
The first is Visitor Screening, which is on every plan. You answer two questions at setup: who your ideal customer is, and who your Aijent should politely screen out. During a live conversation, screening holds back from judging anyone too early, and it only declines a visitor who is not a prospect of any kind: a student or researcher with no buying context, someone asking out of idle curiosity, an obvious test or a bot. Asking to buy, book or start a trial counts as a sign of a real prospect. A real business that is simply a weaker fit is not declined by screening either. It goes wherever your "when unsure" setting sends it: to a person, or onward with the conversation tagged for review.
The second is SureGate, available on Growth and above. There you write firm rules, each a number, an amount of money or a category, and a visitor whose known answers land in a No-go band is declined.
The difference that matters here is the wording. A SureGate decline uses the message you write. A screening decline uses a fixed house line:
"Really appreciate you getting in touch. This might not be the right fit for you right now, but I'm glad to help with anything else you're curious about."
So if you want the no in your own words, that is a SureGate setting. Everything else in this post applies to both.
When the no is said
The most important design choice is timing. The decline is not announced the moment a visitor is out.
The conversation carries on. The visitor keeps asking questions and keeps getting answers. The decline is posted only when they reach for the next step: they ask to book, ask for a call, or ask for the sign-up link. That is when the no becomes relevant, so that is when it is said.
Picture the alternative. A visitor mentions their team size in passing, and the agent replies, "Unfortunately we only work with larger teams." They asked a question and got a rejection instead of an answer. Waiting also means plenty of people who only wanted information get it, and leave without ever hearing a no.
The decline is posted by the system, not improvised by the agent. The agent is never shown the wording or told the visitor is out, so it cannot let it slip early or soften it into a maybe. When the moment comes, your message goes out once, exactly as written. If the visitor has been writing in another language, it is posted in theirs.
How a good decline is worded
The message is short, usually two to four sentences. In that space it has five jobs.
Thank them. "Thanks for the detail" does more than a paragraph of gratitude.
Say who you serve, not what they lack. "We work best with practices that handle business tax" is a fact about you. "Your business is too small for us" is a judgement about them. The second stings, however politely it is phrased.
Be honest that it is not a match. "We might not be the right fit just yet" is honest and leaves room. "Let me see what I can do" is a promise the next message will break.
Point somewhere useful. A guide, a better-suited kind of provider, a directory. A no with somewhere to go reads as advice.
Leave the conversation open. The agent keeps helping after the decline, so the message can honestly say so.
One constraint shapes all of this: one message covers every reason. SureGate posts the same decline whichever rule decided it. That is deliberate, because it means the message can never name the line that fired. It also means you cannot write "we only work in Queensland" if you also decline on project size. Write it about who you serve in general, so it is true for everyone who receives it.
Two things to leave out. Numbers they missed: nobody should read "below our minimum budget". Promises the chat cannot keep: after a decline the agent cannot book, send your link or arrange a call, so the message should not say "someone will be in touch". If they want a person, there is a route for that, covered below.
You do not start from a blank box: a decline is drafted from your SureGate rules and redrafts as they change, until you edit it. Then your words are kept.
Why the visitor keeps getting help
After a decline, your Aijent does not go quiet and it does not show anyone the door. It switches into a plain helpful mode, in the same name and voice, with no visible change.
In that mode it answers questions about your business from your own content, warmly and factually, and lets the visitor lead. It stops asking about their budget, team or plans, stops suggesting a trial, demo or booking, and offers no opinion on whether you suit them. It just helps.
There are four good reasons to keep helping someone you will not meet.
They came with questions. A no to a meeting is not a no to information.
Today's no is often a later yes. A business too small now may not be in a year or two, and how it was treated on the way out is what it remembers.
They talk to people. A visitor who was helped repeats your name. A visitor who was brushed off repeats the story.
It costs you nothing. The expensive thing, a meeting with your team, is the only thing the decline withholds.
Behind the switch, the agent works from a short neutral summary of the conversation so far, because an AI left with the momentum of a sales conversation tends to keep selling. It has no booking tools and no conversion link in reach, and a reply that did contain your link would be replaced with your decline message. The help is real, and the door stays shut.
When they push back
Some visitors ask again, or ask for someone to call. The decline is not repeated, because the same no twice is how a conversation becomes an argument. The next time they ask to move forward, your Aijent replies, "Of course. Pop your details in below and someone from the team will be in touch," and shows a callback form. Once. It never appears a second time, so the conversation cannot loop.
If they fill it in, the request reaches your team through the same channels as any other callback, with a line of context: this visitor was screened below your fit threshold, with the reason where there is one, but asked for a call, and the team decides. If they left an email, they are also sent a copy of the chat.
This is the safety valve for the visitor your rules misjudged. Someone who insists is telling you something, and a person should hear it.
And once a SureGate No-go is reached, a later change of answer does not reopen the booking. A visitor who tries a bigger budget gets the same outcome, which stops your rules being gamed by trial and error. The callback form, where a person decides, stays the honest route.
Why the whole transcript is saved
Every conversation is saved in full, the declined ones included. That is what makes declining safe.
You can audit every no. Read the declines for the first few weeks. If one reads wrong, you can see exactly what the visitor said and move the rule or the wording.
You can see who your website attracts. Analytics labels each screened conversation by fit, with a one-line reason, and lets you filter by it. Read together, the declines show which campaigns pull the wrong crowd and which request keeps arriving that you do not sell.
The record reaches your CRM. With a CRM connected, a conversation of more than a few messages is written to it, with the transcript, even when nothing was booked and no email was given.
The second conversation starts with context. When that visitor returns as a buyer, the first conversation is there to read.
What your team is told
A decline on its own does not send your team an alert. That is deliberate: an email for every no would hand back the time the door policy saved. The declines are in Analytics, and in your CRM if one is connected, whenever you want them.
Your team is alerted when a declined visitor fills in the callback form, because that is the only point where there is something for a person to do.
Six decline messages by industry
These are examples, written to show the shape. They are not taken from any customer. Each would sit in the SureGate decline box, and each is written to work whichever of that business's rules decided it.
1. A bookkeeping and accounting practice
Works with small businesses on ongoing bookkeeping and business tax. Declines one-off personal returns.
"Thanks for explaining where things are at. We work best with small businesses that want ongoing help with their books and business tax, so we might not be the right match for this one. A registered tax agent who handles individual returns would suit you better, and I'm happy to answer anything else here in the meantime."
2. A digital marketing agency
Runs retained campaigns for established businesses with an ongoing media budget.
"Really appreciate you sharing your plans. We do our best work with established businesses running ongoing campaigns, so we're probably not the right fit at this stage. Our guides on getting started with paid search are free to use, and if your plans grow, we'd love to hear from you."
3. A commercial fit-out builder
Takes on office and retail fit-outs in the cities it works in. Declines residential work.
"Thanks for the detail on your project. We focus on commercial fit-outs for offices and retail spaces, so this one sits outside what we do. A local residential builder will serve you better, and you're welcome to keep asking me questions about how fit-outs work."
4. B2B software for sales teams
Built for companies that already have a sales team. Very early startups are not ready for it yet.
"Thanks for telling me about your setup. We're built for businesses that already have a sales team working inbound leads, so we might not be the right match just yet. When that team arrives, come back and see us, and in the meantime I'm glad to help with any questions."
5. An employment law practice
Acts for employers, not employees, and only on employment matters.
"Thank you for explaining your situation, and I'm sorry you're dealing with it. We act for employers on workplace matters, so we're not the right firm to help with this one. Your state's law society runs a referral service that can point you to the right lawyer, and I'm happy to answer general questions about how we work."
6. A corporate events venue
Hosts conferences and corporate functions for larger groups. Declines private parties.
"Thanks so much for thinking of us. We specialise in conferences and corporate events for larger groups, so we may not be the best match for this one. A smaller function space would give your event the attention it deserves, and if you're ever planning something for work, we'd love to host it."
Each thanks the visitor, describes the business rather than the visitor, points somewhere specific and leaves the conversation open. None names a figure or promises a call. The law example adds sympathy, because people who contact a law firm are often having a hard time.
Checking your own no
Before you switch SureGate on, read your decline message against five questions.
- Would you say it to their face? If it would be awkward across a desk, it is awkward in a chat.
- Is it true for every rule? Read it once for each No-go reason.
- Does it describe you, not them? Hunt for "your business" and "too".
- Does it point somewhere? If it ends on "sorry", add a next step.
- Does it promise what the chat cannot do? Take out any call or follow-up you have not arranged.
Then test it. SureGate's simulator takes a hypothetical visitor's answers and shows the outcome and which rule decided it. Run a few near misses through it, then read your real declines in the first weeks and adjust.
Where to start
Turn on Visitor Screening first. It is on every plan, it labels conversations by fit, and it declines the visitors who are plainly not buyers, in the house words above.
When you want firm rules and a no in your own words, write them in SureGate, available on Growth and above. Every plan is on the pricing page.
A warm no is not a softer way of turning people away. It is a different idea of what the conversation is for. The meeting was never the only thing on offer, and the visitor who does not get one can still leave with everything else.



