Configuring the agent

Everything your Inquiry Agent does comes from one screen: Agents → your agent. It's ordered by what weighs the most into three tabs: Essentials, How it talks and Fine-tuning. The configuration is seen and edited by the Owner and the Admins.

Each setting is a row with a question and, under it, what is configured today. Tap the row and it opens in place; changes are saved with Save on the changes bar. On the right you have the Playground, a WhatsApp conversation with your agent: save a change and test it right there, before a customer does.

The agent only knows what you load here — it never fills gaps on its own.

Essentials

The five things that change how it serves the most. If one is missing, a dashed card at the top lists what you still have to complete; once you complete it and save, it goes away.

What does your business do?

Free-form context: what you sell, what you specialize in, what you explicitly don't do. The agent uses it to reason, not to quote verbatim.

Which products can it offer?

By default, the whole catalogue. If you have it split into groups, you choose which groups this agent offers.

Can it share prices?

What the agent can say about amounts:

When does it hand off to you?

Minimum to hand off is what an opportunity has to meet before going to a sales rep. Each piece of data — destination, dates, number of passengers, budget — is marked as Required, Desired, If it comes up or Don't ask.

• With no data marked as Required, every inquiry is handed off.
• Whatever doesn't reach the minimum is held back: the agent keeps the conversation going until it gets what's missing.
• The date of birth is there so you can greet the customer on their birthday. It can be marked Desired, If it comes up or Don't ask, never Required: an inquiry is never held back because the customer would rather not give it. With Desired, the agent asks for it once, saying what it is for, and saves it on the customer's record. If the customer leaves out the year, the agent does not make it up: what they said goes to About this person and the date of birth stays empty.
• Minimum intent sets what the customer has to have done besides giving the data: Asks for a quote, Buying signal, Saw the rate or Wants to book. With Saw the rate, the agent gives the published rate of the product they are asking about and hands off only once the customer keeps the conversation going or accepts the next step. If the product has no price loaded, a buying signal is enough.
• Impact on your recent opportunities, inside this same row, shows you with Show how many of your latest opportunities would have gone to your team and how many would have stayed with the agent with that minimum. Look at it before saving: a very demanding minimum leaves your team without inquiries.

Key facts

The opposite of the row above: answers the agent repeats word for word when a topic comes up — where you're located, how payments work, what your deadlines are. Use this for anything that must always come out the same way. It holds up to 30.

For anything longer than a field — a policy, an operator's conditions, your site's FAQ — there's Knowledge, which the agent searches instead of reciting.

How it talks

How it introduces itself and how it sells.

At the top is Start from a pack: three starting points (First-person seller, Declared assistant, Closed product) that set How it writes, When it replies and how each reply is sent in one go. Closed product also sets How it sells to Closed product, the minimum intent to Wants to book and no field as Required. Applying changes the draft: you see every change below and it only takes effect when you save. You can also pick one when you create the agent.

• How it sells. Tailor-made is the agency process: it understands the trip, quotes options and hands off to the seller who closes. Closed product is for a business that sells its own product with fixed dates or slots (a glamping, a surf trip, a tasting): it presents, gives the price and takes the customer to book, and hands off only when they want to book. It does not change your line of business: a glamping is still Lodging.
• Sales posture. How much it advises before asking for a detail: from Direct (one question per message, hands off as soon as it has the minimum) to Dreamer (sells the trip first and asks only when the customer wants to move forward).
• Tone. Warm (close: it reacts to what the person said and asks with interest), Professional (dry, just the facts) or Lively (effusive, with emojis).
• Name and accent. The name, the avatar, the gender and the nationality. - Nationality. It's not cosmetic: it sets the register. Picking Argentina / Uruguay switches the agent to voseo, not just to a flag.

Fine-tuning

Everything else. It comes well set up out of the box: touch it only if something doesn't convince you.

Greeting and messages

• Greeting. The first message of every conversation. You can write your own with {nombre}, {agencia} and {momento}, and choose whether it replaces the agent's greeting, is added to it, or goes out As written: the system sends it exactly as you wrote it, without going through the agent, with an optional button that opens a link (on WhatsApp it shows as a button under the greeting; on Instagram and Messenger, as a link at the end of the text). If the person asked something specific, the agent answers it in the next message; if they only said hello, it adds nothing.
• How it sends each reply. In a single message or in several short ones.
• Business-specific phrases. Tone notes that are not an option in How it writes («use formal you»).

Words, punctuation and length

• How it writes. Words your agent swaps («tarifa» instead of «precio») or avoids, whether it uses a closing period and semicolons, whether lists use a dash or ✅, the length of each reply, whether it asks one question per message, how it names the customer and whether it introduces itself as a virtual assistant. When asked, it always says it is a virtual assistant. The preview runs a test message through the same setting that is applied before sending.

When it replies

• When it replies. How long it waits before answering: right away, or between 30 seconds and 5 minutes. The wait counts from the person's last message, so if they keep typing it starts over. It applies to WhatsApp, Instagram and Messenger; on your website chat it answers right away. What it does when the person stops replying is set in Automations.

Voice of the audios

Speed and timbre only affect voice notes. A more expressive timbre at a slower speed sounds less robotic — use Listen to compare before deciding.

Your team's hours

• Your team's hours. When someone is available to take a conversation, day by day, in your timezone. Outside that range the agent still answers, and never says you're closed: what changes is that it tells the customer when a person will pick things up. If you have a storefront, its opening hours go in Key facts.

What is sent at handoff

What the customer gets when the inquiry goes to your team: a link, a file, or both — a catalogue, a set of instructions, a booking form. For each one you say whether the customer needs it or it's an extra.

Rules

You write rules in your own words and Trama shows you how it understood them, under We understood it as — read that line, because that interpretation is what actually gets applied.

Sometimes what you wrote is not a rule, and Trama tells you before adding it: if it is about how the agent writes it offers Apply in How it writes, if it is a fact about your business Save in Key facts, and if it bundles several instructions Split into separate rules, interpreted one at a time. You can always pick Keep it as a rule.

Then you choose who resolves each rule. There are three levels, and the difference is real:

• Not every rule can be Mandatory. "We don't sell Japan" or "don't promise instalments in dollars" are concrete things that can be looked for in the message before it goes out. "Be warm in the greeting" isn't: there's nothing to check, and Trama tells you so instead of promising a control it doesn't have.
• Before you turn on a Mandatory rule, you see its effect. Trama runs it against the messages your agent already sent and shows you how many of them would have had a different reply.
• Ask needs a condition that can be checked: a number ("if it's more than 8 people"), a day or deadline ("if it falls on a Saturday", "if there are fewer than 48 hours left"), or a concrete fact in what the customer says ("if they say they don't have a visa"). When it's met, the agent tells the customer it's checking, writes to your team and comes back with the answer.

Each agent allows up to 24 rules, of 300 characters each. If you have several agents, the shared rules apply to all of them and count toward that maximum.

Try it before a customer writes to it

Every change is tested in the Playground, to the right of this screen, without creating opportunities or notifying your team. It's explained in Testing your agent.