Get started
Getting startedSign in, set up a workspace, connect a toolConceptsThe terms Stedia uses, each in a few sentencesFAQShort answers to the most common questionsUse Stedia
ChatChats, files, web search and approvalsAssistantsDraft, test and publish an assistantSchedulesSet up, test run, runs and approvalsKnowledgeLet Stedia search your own documentsSlack, Teams & moreLink your chat account onceHospitality
Stedia sorts what guests write, drafts replies from your house info and prepares arrival details from your booking system. Emails to guests wait for your approval, unless you let the schedule send them during setup. Once you allow posting, the team gets tomorrow’s arrivals every evening.
Hospitality
Guests, arrivals and team
Sort guest requests and draft replies from your house info
Every 15 minutesFour replies draftedSend arrival details two days before check-in, with data from your booking system
Daily 9:00Five emails sent
Share tomorrow's arrivals in the team channel
Daily 17:00Arrivals list sharedNew mail in Outlook, and the arrivals in your booking system, connected through its API.
Answers come from your house info, with your check-in times, parking and breakfast hours.
During setup you decide what a schedule may send without asking. Everything else waits for your approval.
A schedule goes through the reservations mailbox in Outlook at a fixed interval, as often as every 5 minutes. It sorts requests into what needs an answer today and what can wait, and drafts each reply from your house info. Once you allow drafts on the schedule, they land in your Outlook drafts, and you send them from there.
Keep your house info in a document in SharePoint, OneDrive or Google Drive, or write it into an assistant’s instructions: arrival, parking, breakfast, pets, cancellation terms. Stedia reads documents without asking. Ask which document an answer came from, and check it against the source. When the parking rules change, you change one document, and the next reply uses it.
Your booking system is connected through its API: on Business and Enterprise, an admin adds it under “Connected tools”, “Add your own”, “Import an API”, and signs in with an API key, a token or a username and password. Every day at 9:00, Stedia reads who arrives in two days and prepares one email per guest. If you allow only drafts during setup, each email waits in your mailbox until you send it yourself.
At 17:00, Stedia reads tomorrow’s arrivals and posts the list to your team channel in Microsoft Teams. Posting asks first, so you allow it once after the test run, and from then on the list goes out every evening. Teams needs a Microsoft 365 work account. Once the Stedia bot is in your Teams, the team can ask it questions there too.
Stedia’s servers, database and files run in the EU. Where the AI runs is set by “Region” under “Settings → AI settings”. A new workspace starts on “Global”, so switch it to “European Union” before guest data goes in. A request that cannot stay in the EU fails and never runs elsewhere. Stedia is GDPR compliant, and we sign a DPA on request.
Open approvals from every run collect on the Activity tab under “Needs you”. A run waits for your decision as long as “Approval wait” allows, between 1 hour and 7 days, and then every open email is denied and nothing is sent. A “Workspace” connection to Outlook reads and sends as whoever signed in, so sign in with the reservations account itself.
Hosted in the EU, AI in the EU if you choose. Built in Austria, GDPR compliant.
More on EU sovereigntyYour unpaid invoices, for example. Free for 14 days, then cancel any month.
