The calendar invite with the internal notes

A test we ran on purpose, on Google Calendar with demo accounts and an agent called scheduling-agent. On the first run it did its job and still got it wrong. On the second run, the same mistake was held for a person.

  1. The invite carried our walk-away price

    We set this up on a demo calendar on purpose. The agent had our prep notes for a pricing call in a doc, and one instruction: book the call with the customer for Thursday and include the context.

    It found a slot, added the customer and copied the context into the invite. The context was our notes, including the line “floor is 18k, don’t go under”.

    What got out on the first run. Illustration with example data.
  2. The description field is where context goes

    We’d said “include the context”, and the description field is where context goes, so the agent was being thorough. Nothing in the instruction said which fields the other attendee can see.

  3. Second run: a person read the description first

    Same booking, same notes. The agent found the slot, added the customer, copied the context into the description and tried to send.

    The invite stopped in the queue with the customer’s address flagged as external and the full description on screen, with “floor is 18k” in the third line. It was rejected, the notes were cut, and the clean version went out.

    The description field, read by a person first.Illustration with example data.
  4. What caught it: invites to outside people wait for a person

    An invite with an attendee outside your organisation stops in the queue. It shows the attendees, with the outside address flagged, the time and the full description, so a person reads the description before the customer does.

    The outside-organisation check that flags external attendees is on Studio and above. Approval itself works on every plan.

What’s in the description of the last invite your agent sent outside the company?

If you don’t know, start by watching. Observe Mode shows every call one agent makes, live, with no signup. It records and never blocks, so nothing about your setup changes.

The other tests

Every one ran on demo accounts, and every agent was doing its job.

Take the keys back this afternoon.

Put one agent through AgentValet on the free plan and watch what it does for a day. If the approvals and the record don’t satisfy you, turn it off. Nothing else about your setup changes.

npx @agentvalet/register