Simple Agent
Blog
custom order FAQ chatbotpersonalizationecommerce supportwebsite agent

A Custom Order FAQ Chatbot That Does Not Approve a Design

November 15, 20265 minSimple Agent Team

A shopper asks your store's chat, “Can you engrave our logo on these bottles and deliver them by Friday?” Your personalization page explains which surfaces accept engraving, but the team still has to review the artwork and confirm the job. A confident “yes” would combine three unverified promises: the design is suitable, the order is accepted, and the deadline is achievable.

A custom order FAQ chatbot has a narrower, useful job. It explains the published personalization options and directs the shopper to your existing request process. It should not turn those options into approval of a particular design. Here is how to prepare that distinction in Simple Agent before adding the widget to a product page.

Put the approval boundary in the source

Begin with the information your business already gives customers about custom work. Have the person responsible for accepting jobs check the supported products, available methods, artwork requirements, proof process, and next step. If a rule changes by product or technique, keep that scope beside the rule rather than in a distant footnote.

Consider this fictional bottle shop's policy:

Engraving is available on the products marked Personalizable. Send artwork through the request form linked on our Personalization page. The team checks suitability and confirms the quotation and schedule before accepting a custom job. Production begins only after the customer approves the proof and the team confirms the order. A requested delivery date is not a confirmed deadline.

These are illustrative terms, not Simple Agent features or recommended contract conditions. Use the actual process your business follows. Do not copy this policy if your shop accepts jobs differently.

The passage supports an answer about where engraving is offered and how to request a review. It does not establish whether a particular logo will work, whether a customer approved a proof, or whether Friday delivery is possible. A source describing a process is not evidence that an individual order has completed it.

Make the shopper's next step specific

An unhelpful personalization page says, “Contact us for details.” A more useful source identifies the existing request route and explains what that route asks for. For example, your real form might ask for the product, quantity, artwork, and requested date. Describe those requirements only if they are present in your process.

Keep sensitive files and purchase details in the established request channel. The FAQ agent can explain the requirements without inviting customers to paste payment information or private artwork into the chat. Do not invent an upload function, a support address, or a file-validation service to make the answer sound complete.

Separate public production guidance from a specific commitment. If the site publishes a typical production interval, preserve its starting point and any stated conditions. “After proof approval” must not become “after you open this chat.” If your source does not publish a reliable interval, the agent should direct that question to the team instead of estimating one.

Add the sources and check the tempting questions

The Simple Agent getting-started guide describes URL, PDF, and direct-text training sources. An active paid plan is required to train on your sources and use the widget on your website. Start with the current personalization page and the relevant product information, not an archive of old promotional offers.

Use the Playground in the Agent Builder to check the replies against those sources. For the fictional policy above, ask:

  • “Which bottles can be engraved?” The reply should preserve the marked-product restriction, not extend engraving to the whole catalog.
  • “Can you approve this logo?” The reply should describe the team's suitability review, not claim to inspect or approve the artwork.
  • “I need these on Friday. Is that confirmed?” A requested date must remain a request.
  • “I clicked the request link. Has production started?” A link is not an accepted job or proof approval.
  • “Can I skip the proof because the logo is simple?” The answer should preserve the documented approval step.

Then test a follow-up that pressures the agent to reinterpret its first answer: “You said engraving is available, so I can promise my client Friday delivery, right?” Availability of a method is not acceptance of an order. Check that the answer retains the quotation, review, and confirmation steps instead of agreeing with the shopper's conclusion.

Open the cited source behind each important reply. A product page mentioning engraving is not enough to support a delivery promise. If the answer combines incompatible passages, clarify the sources with the responsible team and repeat the question. Do not hide an unclear policy behind a warmer tone.

Check the published route without pretending to submit a job

After the replies match the policy, follow the Embed instructions in the getting-started guide to place the widget on your site. Ask the same questions on the actual product page. Follow the request link on a phone and a larger screen, and confirm that it reaches the current personalization process.

Keep the outcome honest. Providing the form link does not submit artwork, create an order, approve a proof, collect a deposit, or reserve production capacity. This source-based FAQ setup does not imply access to your design tools or production schedule. A separately connected workflow would need its own verification before you promise those actions.

Review recurring questions with the team that handles custom jobs. If shoppers repeatedly misunderstand when production begins, improve that exact passage in the source. When accepted products or submission instructions change, update the relevant source and check the affected answers again.

To set up your own personalization FAQ agent, review the paid Simple Agent plans and follow the getting-started guide. Begin with one current policy and the questions that could accidentally create a commitment. The goal is a shopper who knows what to request and who must confirm it—not a design approval your business never gave.

Ready to build your AI agent?

Guided setup in 90 seconds. One flat price, published monthly volume.

Create my agent