Skip to content

Request an agent

The Agent Hub is a fixed catalogue, so the automation your operation needs may not be on it. Request an agent, at the top right of the hub, files that ask with the people who build the catalogue.

Screen /agents · Roles: anyone who can open the Agent Hub - Point of Contact, Booking Manager, Account Manager, Property Manager, Admin

Everyone who can open the hub, not only the seats that configure rules. Asking for an automation is not configuring one, so the button rides the same permission that let you see the hub at all. That is deliberate: the seats closest to the unmet work, reception and the front desk included, are the ones whose asks are worth the most.

  1. Open the Agent Hub and press Request an agent at the top right. It is there on all three tabs - Agents, Tax, and Run history.

  2. What should we call it? A short name the request can be read by, like “Late-checkout auto-reply”. Up to 200 characters.

  3. What should it do? Describe the workflow in your own words: what starts it, what it should check first, what it should send, and to whom. Up to 5,000 characters. One concrete case you handled by hand last week is worth more than a general wish.

  4. Reply-to email (optional). Where you want the answer. Leave it blank and the address on your seat is used.

  5. Attach screenshots or files (optional). Up to 5 files, as JPEG, PNG, WebP, AVIF, or PDF. The message you retype by hand today, or the spreadsheet you keep beside the product, explains a workflow faster than a paragraph can.

  6. Press Send request. A “Thanks, your request was sent” confirmation appears and clears itself.

Every request carries, taken from your signed-in session rather than from the form:

  • Who asked - your seat’s email address and its roles.
  • Which workspace the request came from.
  • Where you were - the page you asked from, plus the usual browser, screen size, language, and time-zone envelope.

That is so the answer can come back to the right person, and so the same ask arriving from ten operators is visible as one theme rather than ten notes. None of it is read for money or for permissions.

Requests land on a board that Stay N Host reads and triages: new, reviewing, planned, shipped, or declined. There is no request status inside your workspace today, so the answer comes by email, to your reply-to address or to your seat’s address.