> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryecco.com/llms.txt > Use this file to discover all available pages before exploring further. # Where to put information > Which section to use for each type of information, so the assistant always answers the same way. Ecco reads FAQs, documents, web pages, property fields, and procedures together. When the same information is written in several places with different words or values, the assistant may mix them and give an answer nobody decided. > [!NOTE] > > **A real case.** In one knowledge base, the time it takes to send check-in instructions appeared in 24 places, with different versions: “10-15 minutes”, “15 minutes”, “15-20 minutes”, “about 30 minutes”, “noon”, “in the morning”. The assistant answered with one version one time and another the next. The fix was to keep a single version, in the FAQ, and remove the others. There is one rule: **every piece of information has one main place, and that is where you write it in full.** If it also appears somewhere else, for example in a property field, it must say exactly the same thing. ## Where each piece of information goes | Type of information | Where to put it | Examples | | - | - | - | | A rule that is the same for every property | [FAQs](/how-to-use/knowledge-base), one per topic | Check-in and check-out times, late arrival, early check-in and late check-out, deposit and insurance, tourist tax, accepted payments, documents and registration, extra cleaning, pets, house rules | | A detail that changes from one apartment to another | [Property](/how-to-use/properties) fields | How to get in, access codes, address and floor, parking, waste collection, Wi-Fi, appliances, heating and air conditioning | | An exception to a general rule | Property field, written as an exception | “In this apartment, check-in is possible until 9:00 PM.” · “In this apartment, dogs are allowed.” | | What the assistant must do in a situation | [Procedures](/how-to-use/procedures) | Lost keys, a fault or an emergency, a request the team must check, when to hand the conversation to an operator | | Long text to look things up in | **Documents** in Content (the whole account) or **Property documents** (one apartment) | Full house rules, house manual, area guide, booking terms | | Content published online | **Web pages** | Website, menu, price list | > [!TIP] > > **FAQ or procedure?** The FAQ says *what the rule is* (“Check-in is from 3:00 PM to 10:00 PM”). The procedure says *what the assistant does*, step by step (“Ask for the booking number, then hand the conversation to an operator”). ## How Ecco helps prevent conflicts Ecco compares information by meaning, not only by matching words. > **FAQ conflicts** > > When a new, edited, or reactivated FAQ conflicts with an active FAQ, Ecco names it, explains why, and blocks the change. > **Account-wide information** > > When a general field conflicts with an FAQ, Ecco shows a warning with the reason and a link to the related FAQ. A warning means the information was saved. Open the related FAQ and make both versions agree. Fields for one apartment are not compared with the FAQs, because they can contain valid local details or exceptions. ## FAQs * **One FAQ per topic.** If there is already an FAQ about late arrival, update it instead of creating another one. * **One question per FAQ**, phrased the way a guest would ask it. A text about check-in, deposit, tax, and parking should be split into four FAQs. * **The complete rule:** exact values, explicit conditions (“If you arrive after 10:00 PM, …”), and what the guest must do. * **Short:** keep it to about 800 characters. If you need more, split the FAQ or move the details to a document. * **No repeating other FAQs.** If the check-in FAQ also repeats the tourist tax, one of the two will be out of date when the tax changes. ## Property fields * **Each field describes that apartment.** It is the right place for access, codes, Wi-Fi, parking, and amenities. * **General rules in one line.** Some fields ask for a rule that is the same for everyone, such as check-in times, and help complete the property. The FAQ stays the source: in the field, write only one line with the same value (“Check-in from 3:00 PM to 10:00 PM”), never the full FAQ text or an email. When the rule changes, update the FAQ and these lines together. * **Explicit exceptions.** If the apartment is an exception to a rule, say so clearly in its field: the assistant uses the exception for that apartment and the FAQ for all the others. * **Copy to others…** works well for information that is truly identical across apartments, for example in the same building. When it changes, copy it again with **Replace existing values**, so no apartment keeps the old version. ## What not to add > **Messages or emails sent to one guest** > > A text like *“We confirm that payment for booking 29780 has been received”* pasted into the tourist tax field becomes, for the assistant, a rule for every guest. Write the rule, not the message. > **Booking details** > > Booking numbers, guest names, and stay dates are not information about your property. Ecco reads each booking’s details directly from your PMS. > **Many questions and answers in one field** > > A field or document with ten questions and answers is hard to use and to keep up to date. Turn each question into an FAQ. > **Old versions “just in case”** > > When a rule changes, delete the old version. Two different versions of the same rule are the most common cause of wrong answers. > **Internal notes and promises** > > Write only what the assistant can tell the guest. Avoid notes for your team (“ask Marco”) and promises you cannot guarantee (“we’ll call you back within 5 minutes”). ## When something changes **1. Start with the FAQs** General rules should all be there. Update the FAQ for that topic. **2. Check the properties** Look for the old value in the property fields, especially those copied with **Copy to others…**, and update it everywhere it appears. **3. Check documents and web pages** Update or delete documents with the old version. For web pages, update your website first, then select **Refresh now**. **4. Text imported from your PMS** Documents with the PMS badge, for example **Kross**, are updated from the PMS itself. ## When you accept a suggestion * **Choose the right place.** If the information applies to every apartment, select **This applies to every property** and save it as an FAQ. If it applies to one apartment, save it in that property’s field. * **Follow the consistency notice.** Ecco names a related FAQ and explains any conflict. Open that FAQ before deciding what to keep. * **Update instead of adding.** If the suggestion matches an existing FAQ, choose **Update existing FAQ** instead of **Save as new FAQ**. * **Don’t lose information.** If you edit the text before accepting it, check that you have not removed parts that are still needed: Ecco saves the text exactly as you leave it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.