What is useful to add
- Stable conditions for ordering, reservation, payment, or delivery.
- Precise attributes of the specific item that are missing from the description.
- Known condition, package contents, compatibility, or limitations the seller has verified.
- An answer to a frequent question when it is the same for every buyer of that item.
What should not be added
Do not copy the entire listing, turn a temporary agreement with one buyer into a general rule, or add an unverified assumption. Private guidance about tone or persuasion may shape the reply, but it should never appear word for word in a buyer message.
Chat knowledge and listing knowledge
Context marked “for this chat only” helps continue one agreement and remains available in the product card for editing or deletion. Once deleted, it disappears from the list immediately and no longer affects the conversation. General information is added to the listing as a separate paragraph without erasing existing text.
What to do after a listing changes
Sellers often reuse a listing for another model or substantially change its terms. If the new listing conflicts with saved additional information, that information needs review. Vidkov displays a warning in the dashboard and can send it to Telegram so an old fact does not appear in a reply about the new item.
How to write notes that genuinely support a sale
Additional information is for facts that are absent from the public card but regularly matter in seller answers. It is not a second advertisement and not a collection of prepared messages. A good note records the rule, its boundaries, and whether it applies to one item or a group. The model can then write a natural answer for the buyer's actual request instead of copying a fixed sentence.
What should be added first?
Record the actual set, inspection results, available delivery methods, dispatch time, compatibility, warranty conditions, and negotiation boundaries when already decided. Include only commitments the seller will honour. A concrete rule is more useful than adjectives such as “perfect” or “best.”
How should general and product data be separated?
Store rules that apply to every item as general seller information. Put condition, included items, a defect, or a special price beside the specific listing. Shared delivery terms then do not need dozens of copies, and a detail from one unit cannot accidentally appear in an answer about another.
Should example answers be added?
Describe the fact and intention rather than a finished sentence. Buyers express the same question in many ways, so prepared text quickly sounds inappropriate or repetitive. The model should construct the reply itself, using the note as a trusted source and the full chat as its conversational context.
How should limitations be recorded?
Write the positive condition together with its exact boundary, such as when dispatch is available or which models accept an accessory. Do not hide a material condition, but do not fill notes with speculation either. An undecided commercial choice must remain a question for the seller.
How often should notes be updated?
Update after a change in price, stock, included items, collection method, or a shop rule. A short regular review helps active catalogues. Delete obsolete information instead of placing a new claim next to it: two conflicting versions force clarification of something the seller already knows.
How can the quality of a note be tested?
Imagine three different buyer questions that require this fact. If the note supports a precise answer without another guess and does not impose one repeated phrase, it works. After saving, run a controlled conversation using the exact listing to which the information belongs.
Poor ways to maintain additional information
- Copying the entire public description into a note and creating two versions of the same facts that later diverge.
- Saving finished advertising phrases instead of conditions, making answers sound identical regardless of the buyer's question.
- Mixing shop-wide rules with the condition of one unit and accidentally transferring its details to other products.
- Adding an unverified assumption as a fact or promise that the shop cannot fulfil after the buyer places an order.
- Leaving old prices, timelines, or stock next to new data and expecting the system to guess which conflicting entry is current.
Structure a note for quick review: one fact or rule per line, a clear scope, and its current value. Dates are useful only for temporary conditions such as a promotion or closure; remove that condition afterward. If staff members make different decisions, agree on the rule first and then record it. Notes should not conceal a weak public card: put a specification every buyer needs into the listing itself. Test the result with differently worded questions, including short follow-ups to an earlier reply. The model should use a fact only when it serves the request, not paste the entire list into each message. Well-maintained additional information gradually becomes a concise set of precise rules rather than an archive of old replies. That strengthens buyer trust and reduces unnecessary decisions reaching the seller.
During review, identify whether each rule belongs to the public listing, a shop-wide policy, or one particular unit. Buyers never see these internal distinctions, but they help staff update the right layer. If a condition applies to several but not all items, attach it to each relevant position rather than declaring it universal. After removing an old rule, test both a new chat and a continued one so neither revives stale information.