The note is the source of truth.

What to paste

Paste facts. Do not paste a slogan and hope for a policy.

• The current price and what it includes.
• The URL you want sent.
• Hours, cities, and what you do not offer.
• The language, if you want Hindi or Hinglish.

Maintain a compact factual note, not a vague sales script

The knowledge field is pasted text, up to 8,000 characters. Organize it around the facts a customer needs: current offers, exact prices and currency, service areas, operating hours, supported links, and limitations. Include what is unknown and when a human must confirm. A URL written in the note is a supplied destination, not a promise that DripDM crawls the website. Generation uses the supplied context and may still make mistakes, so the note is an input to review rather than a guarantee of correctness.

A workflow to try

Create a short internal source sheet for one offer, then paste only the maintained facts into the rule. State the date-sensitive items explicitly and nominate someone to update them before a launch. Test a question that the note answers, one it cannot answer, and one asking to override the price. Read the full output and open every destination. Keep private customer details out of a reusable business note; recent live conversation history is handled separately by the reply service.

Checks before you change the setup

When facts change, update the note and rerun the relevant previews rather than relying on an old successful test. A blank note leaves the model without business facts even if the goal sounds confident. Do not claim an enforced allowed-links list or automatic website synchronization. Keep both fallback and static text safe because provider errors, caps, and noise can choose different non-generated paths. If precision is critical, use fixed text or human handling instead of open generation.

A small note outline you can maintain

Organize the field into offer, price and currency, included items, dates or hours, service area, approved destination wording, known exclusions, and questions requiring a person. Keep a source owner and review date in your internal maintenance process. Do not add secrets, customer records, or entire unrelated policy archives simply because the field accepts text. When the answer needs precision, verify whether fixed wording would be more appropriate. Test that the note distinguishes a published fact from an estimate and an action request from an action confirmation. Clear source organization makes factual repair easier when real conversations reveal a missing condition.