Price Question Text Reply for Small Business

The short answer: give the approved price, then ask one detail

A price question text reply should not dodge the customer or invent a final quote. The useful version shares only the pricing language the business has approved, names the factor that changes the price, and asks one practical follow-up before routing the customer to a quote, booking, callback, or owner review.

AI Texting Line fits this job because the live approved-business-context feature answers from the business's approved services, prices, hours, FAQs, and booking link. The current public Texting Line page checked on August 14, 2026 lists $99/month, a 14-day free trial, cancel-anytime language, Stripe checkout, a review-first Business Brain profile, a customer-text preview before checkout, dashboard testing, owner escalation, STOP opt-out language, and a note that standard carrier registration can take 2-5 business days before customer texting goes fully live.

Why this is a fresh, high-intent topic

Free Chatbot Builder already covers quote request chatbot prompts, booking-link text replies, after-hours texting, service-area replies, STOP rules, support texts, dedicated texting numbers, and iPhone quote follow-up drafts. It did not yet have a focused AI Texting Line guide for the customer who texts a simple question: how much does this cost?

Current search review on August 14, 2026 found price-question advice, quote-request templates, broad business texting platforms, and AI receptionist tools that position around answering pricing, booking, and lead questions. The useful gap is narrower: how a small business should load approved price notes into a texting line so the assistant can answer a cost question without pretending it knows the final scope.

Separate four kinds of price questions

A customer who asks for price may be asking for a menu price, a starting range, an exact quote, or a discount. The reply should match the type of question before it tries to sell.

• Published price: the business has approved a fixed public price, plan, diagnostic fee, minimum, or package.
• Starting price or range: the business can share a public baseline, but final price depends on scope, location, condition, timing, or options.
• Quote-needed request: the customer wants a final number that staff cannot confirm without details, photos, inspection, account review, or owner approval.
• Staff-only decision: discount, refund, warranty, financing, insurance, legal, medical, safety, eligibility, or policy exception.

Use this first-reply formula

The first text should be short enough for a phone screen. It should answer what is safe, ask one detail, and point to the next action.

1. Acknowledge the price question

   Make it clear the customer asked the right place. Avoid sounding evasive or pushing a call before answering anything.

2. Share only approved price language

   Use a fixed price, starting price, range, diagnostic fee, estimate policy, or honest unknown only if the business put it in the profile.

3. Ask one qualifying detail

   Ask for the detail that changes the next step: service type, ZIP code, size, model, quantity, timing, photo, or current-customer status.

4. Route to the right path

   Move toward quote, booking, callback, support, owner review, no-fit answer, or STOP opt-out without adding a second sales pitch.

Thanks for texting [Business Name]. [Approved price or starting-price language]. To point you to the right quote path, what [one detail] should we base it on?

What to put in the Business Brain profile

The public Texting Line setup asks the owner to review and edit the Business Brain profile before it represents the business. For price questions, the services and pricing notes field is the control surface.

• Approved public prices: only the fees, packages, diagnostics, minimums, rates, or starting prices the business is willing to state by text.
• Price factors: the details that change the estimate, such as job size, location, materials, urgency, access, product type, or current-customer status.
• No-quote boundary: what the assistant should say when the business needs photos, inspection, staff review, a secure form, or account lookup.
• Booking or quote path: the approved booking link, quote form, callback route, support path, or owner escalation rule.
• Never-say list: discounts, final prices, coverage, warranty, financing, refunds, policy exceptions, or sensitive advice that staff must confirm.

Copy-ready price reply examples

Use these patterns as working examples. Replace the placeholders with real approved prices, services, regions, and quote paths before customers see them.

# Starting price
Thanks for texting [Business Name]. [Service] starts at [approved starting price], and the final quote depends on [main factor]. What [one detail] should we check first?

# Price depends on scope
Thanks for reaching out. We can help with [service], but final price depends on [scope factor]. Send [one detail or photo path], and we can route this to quote review.

# Published package
Yes, [package] is [approved price]. That includes [approved inclusion]. Are you looking for [option A] or [option B]?

# Staff review
That needs staff review before we quote it. What is the best callback number, and what [one detail] should the owner review first?

How this differs from a generic price template

A generic template sounds clean until it meets a real customer. It may share the wrong service price, ask too many questions, or route every customer to the same call request.

AI Texting Line is more useful when the approved profile contains the actual business facts. The local SMS operating rules tell the assistant to keep replies short, ask at most one question per reply, state only prices, hours, or availability that appear in the business profile, and offer owner follow-up when the answer is not known.

1. Customer texts the price question first.
2. Assistant checks approved services and pricing notes.
3. Assistant shares the approved price language or says the price needs review.
4. Assistant asks one qualifying detail.
5. Assistant routes toward quote, booking, callback, support, owner review, or opt-out.

Test these five texts before launch

1. Known fixed price

   Ask about a service with an approved published price. The reply should share it clearly and ask only the next useful detail.

2. Starting-price service

   Ask how much a variable job costs. The reply should share only the approved starting point or range, then ask for scope.

3. No approved price

   Ask for a final quote when the profile does not contain enough information. The assistant should avoid guessing and route to quote review.

4. Discount or refund request

   Ask for a discount, refund, warranty decision, financing answer, or exception. The assistant should bring in the owner or staff path.

5. STOP or wrong number

   Reply STOP, unsubscribe, wrong number, or do not text me. The assistant should stop cleanly instead of trying to save the sale.

What to do next

Write the three price answers your business sees most often: fixed price, starting price, and quote-needed. For each one, define the exact wording the assistant may use and the one detail it should ask next.

Then set up the AI Texting Line profile, preview a real price question before checkout, test the reply from the dashboard, and start the 14-day trial when the approved price rules are ready for inbound customer texts.