Owner and team guide

Understand the whole workflow.

ResolveStay helps a manager organize a property problem, decide the next step, coordinate a provider, verify the result and retain the lesson. The manager remains responsible for decisions.

Start with one guest’s air-conditioning problem

  1. 1. Report and review. Record the issue and confirm the evidence.
  2. 2. Decide and assign. Approve a plan, then offer a job to a suitable technician.
  3. 3. Follow and verify. The technician reports progress; the manager checks the result.
  4. 4. Record and learn. Save the outcome and review the team’s feedback.

Know which records you are using

Practice on this device: incident demo, demo memory, sample jobs and manual local contacts. They do not automatically sync to other people.

Shared with the authorized team: registered properties, approved-provider jobs, tenant requests and shared training records. Notification delivery still needs verification.

Before using real customer data: verify team access and the complete job workflow. This deployment has one company workspace, not separate workspaces for unrelated customers.

Choose the part you want to learn

Open a section for instructions, what each action does, and its current limits.

1. Start with the incident workspace

Use an example or create an incident with the guest’s name, property/unit, problem type and description. The incident queue lets you return to a case. The supplied guests, reservations and past outcomes are fictional practice records.

Review the extracted facts and evidence. Yes means confirmed, No means ruled out, and Unknown means you still need to check. Changing evidence changes the rule-based recommendation and risk level. Do not turn a guess into a confirmed fact.

Approve Recommendation records your decision. It does not automatically contact a worker, issue a refund or fix the problem. Modify currently records a modified status; adjust the incident evidence and dispatch instructions yourself. Escalate records a reason for human attention; it does not call emergency services.

Dispatch Cleaner / Maintenance carries the incident details into a draft in Operations. Review the property, service area, worker and instructions before offering the job. This handoff uses the same browser. Incident-demo records and its memory are saved on this device, not shared with coworkers.

Open incident operations
2. Register your properties and operating instructions

An authorized team member with write access can add a hotel, apartment or rental by entering its name, city, region, country and time zone. You are not limited to the three example properties. In dispatch, you can also type a property name directly.

Add operating standards and checklist instructions for the property. Keep them specific: what must be checked, who confirms it and when to escalate. The inventory section stores supply quantities and low-stock levels; update quantities when stock changes. A low-stock warning does not buy supplies for you.

Registered properties, standards and inventory use the shared company workspace. Registering a property does not connect its Booking.com, Airbnb or Hostaway account.

Open property control center
3. Give the right people access

The owner authorizes staff by email. Managers and dispatchers can perform permitted operational updates; viewers can read shared records. Use the authorized account when signing in. Giving someone the public website address alone does not grant team access.

This deployment currently has one company workspace. Invited staff can see its shared records. Separate workspaces for unrelated customer companies are not yet implemented. Do not mix different clients’ private data here.

A provider uses their private job-portal link instead of receiving manager access. A tenant uses a property-specific reporting link. Keep private links private: possession of a provider link grants access to that provider’s jobs.

Open team workspace
4. Bring in the manager’s existing cleaners and technicians

Start with people the property manager already trusts. Send them the provider application. They enter their contact details, service type, location, service areas, languages and availability. The owner reviews the application before approving it.

Approved providers receive a private workspace link when notification delivery is configured. Test that the actual worker receives and can open it before relying on the service. Software approval does not certify qualifications, insurance or background checks.

Manual contacts in Operations are different: they are local to this device. The sample workers, ratings and response times are fictional. Recruit a backup provider only when you identify a real gap in area, skill or availability.

Open provider application
5. Match a provider and offer a job

Choose the service team, property/unit, service area, priority, preferred language, instructions and target ETA. Use a precise location such as Fayetteville, North Carolina, USA. Cleaning, maintenance and transportation are service categories; adding transportation does not book a ride automatically.

The matching list ranks providers using service type, text-based area matching, language, entered availability and other stored attributes. The match percentage is a rule-based ranking, not a probability or guarantee. Check the actual address, skills and availability yourself; this is not live GPS or a travel-time calculation.

For an approved network provider, the signed-in workflow saves a shared job offer and attempts its notification. Read the notification result. A saved job is not proof that an email was delivered, read or accepted.

For a local contact, WhatsApp, SMS, email-app and phone controls open a message or call for you to review and send. Opening the button is not delivery confirmation. Avoid sending the same request through multiple channels without checking what already happened.

Open operations and dispatch
6. Track the worker and verify the result

The approved provider opens their private link, reviews the offer, and accepts or declines. They then report On the way, On site and Completed, with completion notes and evidence where available. These are worker-reported updates, not automatic location tracking.

The shared Operations board refreshes every 30 seconds while open. Use Refresh shared jobs to check sooner. The manager reviews the completed work and marks it Verified. Completed means the worker reports it is done; Verified means the manager has checked it.

If a provider declines or cannot attend, review another suitable provider and arrange the replacement. Do not assume automatic reassignment. Confirm that the property is safe and ready before telling the guest the incident is resolved.

Open provider portal
7. Use Worker job guide as a guided checklist

Open Worker job guide from a job to carry over its property, issue and assigned person. It offers safety prompts, task steps, a checklist and browser-supported voice controls. Voice recognition currently uses English and depends on browser support.

Its checklist and progress controls are a guided working session. Changing Worker job guide’s status does not update the shared provider-job status. For the authoritative job update, the worker uses their private provider portal.

Workers or managers can suggest a phrase and useful response as a training example. Shared saving and approval require appropriate team access. A locally saved example is not the same as a successfully saved shared example. Approved examples do not retrain a general AI model.

Open Worker job guide
8. Record the outcome and use Resolve Memory

After the incident, record whether it was resolved, the time taken, what action worked, the provider, cost, guest rating and learning notes. Ask each involved person what they observed, what helped and what should improve. Review team feedback before using it as a lesson.

Resolve Memory compares saved cases by incident type and property/unit, with additional preference for resolved and helpful outcomes. Its question box recognizes supported topics such as fastest resolution, lowest cost and provider performance. It is a structured, rule-based memory tool, not an unrestricted general-purpose chatbot.

Applying a past case presents that precedent for manager review; it does not prove the same diagnosis or automatically execute its instructions. The combined team feedback displays reviewed suggestions. These demo outcomes and feedback are device-local; separate shared Worker job guide training records do not automatically merge into this memory.

Open Resolve Memory in the incident workspace
9. Let tenants submit maintenance requests

An authorized manager creates a reporting link for a registered property. Give the tenant that property-specific link rather than the manager dashboard. The tenant enters their unit, contact details, issue and supporting photo where available.

The submitted request is stored in the shared queue and has a private tracking link. The manager reviews it, updates its status and public-facing message, and can link an appropriate job for the same property/unit. Submission alone does not guarantee dispatch or an appointment.

For immediate danger, follow the property’s emergency procedure and contact local emergency services. Do not wait for an app response.

Open tenant maintenance
10. Read reports and understand integrations

Analytics summarizes shared records: properties, approved providers, jobs by status, provider job counts and low-stock items. It does not combine all local demo activity or prove customer revenue gains. Read Completed and Verified as distinct statuses.

The incident workspace’s PMS sync validates sample reservation records. It is not evidence of a live Hostaway or Booking.com connection. The call-summary feature summarizes pasted text using rules; it does not answer live phone calls.

An integration indicator can show that configuration values exist. It does not prove end-to-end delivery. Before a real pilot, test intake, access, a provider offer, receipt, status updates, completion evidence and manager verification with the actual team.

Open analytics
11. Choose a language

English is the starting language and the built-in feedback examples are in English. The existing options remain English, Italian, Spanish, French and German. In Resolve Memory choose the section’s language; for feedback choose the language of the text you are entering. In Operations choose the report language and the job’s preferred language separately.

These controls have different purposes. The Memory language changes selected labels and prompts; feedback language identifies the submitted text; job language helps matching. Original user-written text is preserved. They do not translate the entire website or every answer.

Operations recognizes a limited set of common issue words in the supported languages for routing. It is not a fully connected professional translation service. Confirm important instructions with someone who understands the language before relying on them.

Open language controls

Practice before a sales call

  1. Use fictional information in Incident operations. Read the AC case aloud and explain the evidence.
  2. Change one evidence answer and explain why the recommendation changes.
  3. Approve the plan, then open dispatch. Explain that approval and sending a job are separate steps.
  4. Show how you would choose a technician by service area and language. Do not send a real offer during practice.
  5. Explain Offered, Accepted, On site, Completed and Verified, and who updates each one.
  6. Record a fictional outcome and show how Memory brings back a comparable past case.

A useful discovery question: “When a guest reports a problem today, how do you know who accepted it, when they will arrive and whether it was actually fixed?”

The Pilot program page introduces the proposed pilot. It is not proof that a customer has signed, paid or been onboarded. Confirm scope, access, price and readiness separately before starting.