Admin panel
Our take on AI for your guests during their stay. Pick a property to open its dashboard. Changes go live immediately — no redeploy, no code.
Sign in
Enter the admin password to manage properties, guest questions and outreach.
The password is the ADMIN_PASSWORD secret set with wrangler secret put.
Properties
Every property the text line answers for. Open one to edit its answers and gate codes.
Settings
Property details & policies
Keep these details accurate and host-approved. Critical access and emergency instructions are staged for review before they go live.
Host escalation notes
These notes are included in host alerts only. Emergency and high-risk situations are always escalated; this setting cannot disable routing.
Gate & door codes
Released only on an exact keyword match — never sent to the AI, never logged. Empty rows are skipped on save.
Answers
Canned replies matched by keyword — instant, and free. One row per topic. Empty rows are skipped on save.
Knowledge import & export
Use JSON with secrets and answers arrays. Exported files include access codes: store them securely. Imported codes and critical answers are staged for review before they go live.
Google Workspace email
Checking connection…
Leads
Independent Central Florida operators, with linked public sources to recheck before contact.
Guest activity
Last 30 days across your live properties.
Guest questions
What guests actually ask, and where the answers run out. Counts only — no guest names, numbers or message text.
Ranked by how often a question escalated or was never routed to an answer — the themes to write answers for next.
Operations
Guest and AI activity over the last 24 hours; host reply time over 30 days. Guest numbers and message contents are never shown here.
Simulation only: this does not call AI, send SMS, or write message logs.
StayXI Property Pilot Program
Validate whether StayXI can reliably reduce routine after-hours guest questions for independent vacation-rental operators—and whether operators will pay to continue.
Format: 30 days, 3–5 properties, one property per operator to start. Use the pilot records below to set up, launch, measure, and close out each property.
This pilot covers current automated property-specific text support only. Confirm the working contact information, SMS setup, and written pilot terms before onboarding an operator.
Test / demo properties are fine for exercising setup and checks. Do not launch a test property on a guest-facing number or share its number with guests; only activate a real operator property after they approve the configuration and the launch checklist is complete.
Pilot properties
Start a record from an inactive property. Launch is blocked until the operator and property setup are verified and all required checks are complete.
Offer and scope
- Test price: $49 per property for the first 30 days, setup included. This is a hypothesis, not a validated long-term price.
- Invoice manually before the pilot. No automatic renewal; after day 30, stop or separately agree with the operator on any continuation and its price.
- Configure a guest text line with operator-approved property answers and test it with the operator.
- Escalate unsupported or uncertain questions to the operator's configured contact. The property dashboard shows message, answer, and escalation counts where recorded.
- Guest SMS/data rates may apply according to the guest's mobile plan.
Not included unless separately agreed in writing
- Human StayXI coverage 24/7, emergency dispatch, or guaranteed host response times.
- Live weather/hurricane alerts; reservations or tickets; grocery delivery or pre-stocking.
- PMS, booking-channel, smart-lock, or payment integrations; a guarantee that every answer or message will succeed.
The operator remains responsible for the property, guest safety, emergency instructions, accurate supplied information, and responding to escalations.
After launch: learn from real needs
During weekly reviews, manually look at recorded questions and escalations alongside host feedback. Track recurring themes, approximate frequency, whether the current service answered or escalated them, and the operator's view of their value. Keep guest names, phone numbers, access codes, and full transcripts out of the internal needs backlog.
This discovery will help prioritize possible paid add-ons, such as a grouped guest-question insights report, optional answer-library tune-ups, or portfolio-level trends. These are ideas only—not included, available for purchase, or promised. Build and test an add-on, validate its cost to serve, and disclose its price before offering it.
Recruit operators
Start with independent hosts and small vacation-rental managers in Davenport, Kissimmee, and greater Orlando. Look for operators who receive after-hours guest texts, can approve the property information, have a reachable escalation contact, and will give weekly feedback.
First outreach
Verify the business and contact details through its official public channels; personalize outreach, respect contact preferences, and stop if they decline. Do not send unsolicited marketing texts. Confirm hello@stayxi.com works before using it as the reply address.
Discovery questions
- What guest questions did you receive most recently after hours?
- How many guest messages do you handle in a typical week or stay?
- Which questions take the most time, and which are risky to answer incorrectly?
- What happens when you are unavailable?
- What tools or automation do you already use?
- What would have to improve for you to pay to keep a service like this?
Before launch
Document the property, dates, fee/payment, escalation expectations, data/contact responsibilities, and cancellation terms in a written pilot agreement. This dashboard guide is an operating plan, not legal advice or a substitute for that agreement.
- Confirm operator, property, pilot dates, fee, payment, and written terms.
- Confirm working contact addresses and phone numbers for the operator and StayXI.
- Verify deployed SMS endpoint, Twilio number, signature validation, and outbound replies.
- Review HELP/STOP behavior and applicable SMS terms and privacy notice.
- Explain that pilot questions, escalations, and host feedback are manually reviewed for service improvement and possible future feature planning.
- Configure the property; mark it live only after tests pass.
- Collect only facts needed to answer routine guest questions; operator approves all answers.
- Keep entry codes in protected configuration; test exact matching and ensure codes are not exposed to AI.
- Test common, unsupported, and high-risk questions, escalation delivery, and opt-out.
- Provide a way to report incorrect answers and promptly pause the text line.
- Remove demo phone numbers and sample codes from anything guests could mistake for real property information.
If an access-code, safety, privacy, or material-answering error occurs, pause that property's automation, notify the operator, investigate, and agree on a safe restart. Never count an uncertain answer as a successful one.
Measure the pilot
Record a baseline before launch, then review each property weekly. Do not count website demo activity or sales leads as property usage.
| Measure | Record |
|---|---|
| Guest message volume | Incoming guest messages for the property. |
| Automated answers | Incoming questions answered from approved property information or AI. |
| Escalations | Questions routed to the operator. |
| Answer quality | Operator-reviewed sample rated correct, incomplete, or incorrect. |
| Host effort | Operator estimate of time spent on questions before and during pilot. |
| Safety/privacy | Every incorrect access, safety, privacy, or policy answer and its resolution. |
| Adoption / continuation | Whether the line was shared with guests and whether the operator would continue under a separately agreed offer. |
| Cost to serve | SMS, AI, onboarding, support, and other direct per-property costs. |
Proposed decision gates (hypotheses, not results)
- Safety: zero incorrect access-code disclosures and no unaddressed critical safety/privacy incidents.
- Quality: at least 90% of reviewed supported answers rated correct; unsupported questions escalated rather than guessed.
- Value: target at least 50% reduction in host time on routine questions where baseline volume supports a fair comparison.
- Commercial: 2 of the first 3 operators, or 3 of 5, explicitly choose to continue under a separately disclosed offer after day 30.
- Margin: delivery/support costs are known and leave viable gross margin at a price operators accept.
If volume is too low, mark a measure inconclusive—not passed. A safety-gate failure means pause and fix before expanding.
30-day cadence and closeout
| When | Activity |
|---|---|
| Before day 1 | Interview, agree terms, record baseline, configure/test, obtain approval, collect pilot fee. |
| Days 1–7 | Start with one property; verify message delivery and escalation flow. |
| Weekly | Review counts, answer samples, host effort, issues, and configuration changes. |
| Days 28–30 | Review results and costs; ask whether the operator would consider a separately priced continuation. |
| After day 30 | Stop or continue only by explicit agreement at a separately disclosed price; document learnings before recruiting more. |
Ask at closeout
- Did StayXI reduce time or interruptions from routine guest questions?
- Which answers were useful, missing, or incorrect? Were escalations timely and actionable?
- Did you feel comfortable sharing the line with guests? What did StayXI cost you in time or other work?
- Would you continue after the pilot at a separately agreed price? What monthly price would feel fair?
- Which recurring guest needs or unanswered topics would be most valuable to address?