A CPA explains the difference by treating a question as a way to see whether work might fit, and an engagement as the work you have accepted with a scope. The website should say that line in plain words. A stranger can ask enough to find the path, but they do not receive the work by asking. The page, the reply, and the work you sign have to draw the same line.
This guide covers what a question is on your site, what an engagement is, how the page draws the line, what the reply to a stranger should say, and how to test the line with your inbox.
Takeaways
- Call a question what it is: a step to see whether an engagement might make sense.
- Describe an engagement as scoped work that starts only after you accept it.
- Put that line on the page, and use it again in every reply to a stranger.
- Sort the inbox against the line, and change the sentence that keeps getting crossed.
What a Question Is on Your Site
A question on your site is an inquiry about whether you do a kind of work, and whether a conversation is the right next step. It is initial contact. It can be a sentence in a form, a short email, or a call that asks what an engagement would cover, and it ends when the person knows the path or knows they are outside it.
Say what kinds of questions you will hear: someone unsure whether their situation belongs with you, an owner asking which door is right, or someone checking whether you take that work in season or through the year. Those are questions about fit.
A question is not a request for the technical answer, the position, or the finished deliverable. People will still send those, because they are worried and the inbox looks like a shortcut. The site's job is to say, before they hit send, that a technical answer lives inside an engagement. When the page is quiet, every worried email becomes work you never accepted.
Keep the question small: name, how to reach them, the situation in a few lines, and what they think they need. Documents and a full narrative wait until you are talking about scope, because asking for the whole file at this stage teaches people that the work has started.
What an Engagement Is
An engagement is the work you have agreed to do, with a scope you and the client both understand, after you have said yes. It is implementation of that agreement. It is not the email that asked the question, and it is not the first call that explored whether the question belongs with you.
The scope is what makes it an engagement: which work, for which period or situation, with which responsibilities on each side. You do not have to publish the scope on the website, but you do have to publish that a scope exists and that it comes after a conversation, not before. Visitors should expect a detailed discussion between the question and the start of the work.
Acceptance is yours. A polite reply, a booked call, or a request for documents is not a yes, and you should say that where people will see it, because many of them will treat any response as the start. The engagement begins when you confirm the scope and agree to proceed. Until then you are still in the question, even if the question is long.
Follow-up inside an accepted scope is part of the engagement, and a stranger's question is not. A client has a path to you, and a stranger has a path to a fit conversation. Mixing those paths fills the inbox with work that has no scope behind it.
How the Page Draws the Line
The page draws the line by stating what a visitor may ask before you are engaged, and what starts only after you accept. Put it high enough to be seen, in words a worried person can use, because clever phrasing loses to a clear one: "Ask us whether this work is a fit. Answers that depend on your facts come after we agree on the engagement."
Show the path in order. Someone sends a question, you look at whether the situation is work you take, and if it might be, you have a detailed discussion and, if you accept, an engagement with a scope. If it is outside what you do, you say so and stop. That order is the whole explanation, and you should repeat it on the service page for each kind of work, so a tax conversation and a bookkeeping conversation do not share one vague door.
Accounting Firms often feel this when several services sit on one site. A question about books and a question about a filing are different engagements, and the page should say which door is which. A CPA page can be narrower and still needs the same line, since the visitor should know they are asking a question and know what would have to happen before any work begins.
Leave a visible stop for people who want the answer without the engagement. Write it the way you would say it on a call: you are glad they asked, and the answer they want is the work itself.
| What they sent | What it is | What happens next |
|---|---|---|
| Do you take this kind of situation? | A question about fit | You say yes, no, or that you need a short conversation to tell |
| Here are the facts. What should I do? | A request for the work, sent as a question | You point back to the line and offer a fit conversation if the work might follow |
| We already agreed. Here is the next item. | A question inside an engagement | It follows the scope you accepted |
| Can you just look quickly? | A request to start without a scope | You restate that a look is the engagement, or you decline |
| Which page is my job? | A question about the path | You point them to the service that matches, still as a question |
If someone who sees the inbox cannot tell the rows apart, the page is not drawing the line yet. Add the sentence and read the table against real messages.
What the Reply to a Stranger Should Say
The reply should say which row they are in and what the next step is. For a fit question, thank them, mirror the situation in a phrase, and offer the conversation or a clear no. For a technical question from a stranger, thank them and restate the line: you can talk about whether an engagement makes sense, and the answer they pasted belongs inside that engagement if you both proceed.
Keep the reply short enough that you are not doing the work inside it. A paragraph that starts to analyze the facts has crossed the line, even if you end with "of course this is general," because the stranger will treat the analysis as the answer and you will have accepted an engagement you never scoped. Stop at the path.
Use the same words as the page. If the page says "fit conversation," the reply says that too, and names the kind of work. A reply in a new dialect teaches people to ignore the site, and for many readers the reply is the page they actually read.
When you decline, decline the situation, in one or two sentences with the boundary and a stop. Offer another path only when you truly have one. If you need more information to know the row, ask for the situation in a sentence, since a document request makes people believe the work has started. Save that request for the detailed discussion, and say the conversation is still not the engagement.
How to Test It With the Inbox
Test the line by reading recent messages and marking which ones were questions, which were engagements in disguise, and which replies crossed the line. The inbox is the record of what the page taught people to send. You do not need a report, only a pattern you can point at.
- Take the last few stranger messages and write what they were asking for, in a few words each.
- Mark each one as a fit question, a request for the answer itself, or something that belonged inside an existing engagement.
- Open the reply you sent and mark whether it stayed on the path or started the work.
- Open the page they would have seen and copy the sentence that should have set their expectation. If that sentence is missing, write it.
- Rewrite the page so the line is visible before the form, and rewrite your reply snippets to match the table.
- Use the new reply on the next messages, and see whether people still paste the whole problem as if you had already accepted it.
- If they do, the line is still too soft or too low on the page, so move it up and make the form ask "what kind of work are you asking about" before it offers a blank box for the story.
Do the reading before the busy season, when every message feels urgent and the line gets waived. A pattern in older messages is enough to justify the rewrite. Share the snippets with anyone who might hit send, because a careful page and a colleague who answers the technical question anyway will retrain people quickly. If the line only lives in your head, the inbox will not show it.
How the CPAs Page and This Article Split the Job
The CPAs page is the offer. It says this trade is work Triwave Consulting does, as part of Financial & Professional Services. This article teaches the decision on your site: how to separate a question from an engagement so strangers stop treating the inbox as the work.
Read the offer when you want to know whether help with that path is in scope, and read this article when you are writing the line and the reply. You still draft the scope in the detailed discussion, after the question has done its smaller job.
If you want help, the order is initial contact, then a detailed discussion, then implementation. You describe how the inbox behaves now, and together you put the line where a stranger will see it and set replies that repeat it. Implementation is the page and the snippets changed, and the next messages are the test. When they arrive as fit questions, the line is holding, and when they arrive as unpaid work, it is not.
Keep the technical judgment inside the engagement you accept. The site can name the kinds of work and the order of contact, but it should leave the position, the calculation, and the advice for the relationship that has a scope. That limit is what the line is for.
Questions
Can You Answer a Short Question Without an Engagement?
You can answer whether you take that kind of work and what the next step would be, and a short question about fit is the point of the page. A short question that asks for the technical answer is still the work, even when it looks small, so point it back to the line and offer a conversation only if an engagement might follow.
What If the Question Is Really a Request to Start?
Treat it as a request, and reply with the path. Thank them, name the kind of work, and say that starting means a conversation and then an engagement if you accept. If they send the file again, restate the line and wait, because starting by accident is still starting.
Should the Contact Form Use the Word Engagement?
Use it if your visitors will understand it, and pair it with plain words, since "we will talk about whether an engagement makes sense" is clearer than the word alone. The form can ask what kind of work they are inquiring about, and the label should not suggest that submitting it opens the engagement.
How Is This Different for an Accounting Firm?
The line is the same, but the doors may be more than one. An accounting firm that offers books, a filing, and an advisory conversation needs each door to say what the question is and what the engagement would be, while a CPA with a narrower practice may have one door and the same distinction. In both cases the stranger should see the line before they write.
When Do You Close the Thread?
When you have given the path or the no, and the person keeps asking for the answer itself. One restatement is respectful, and a second long exchange becomes the work. Tell them the thread stays closed unless they want to talk about an engagement, then stop typing.
Conclusion
A question finds out whether an engagement might fit, and an engagement is the scoped work you accept after that. Put the line on the page and in the reply, and the inbox can bring fit conversations while the work starts when you say it starts.
If strangers still receive the work by asking a question, Speak With Us.
