Using the app

Sandbox CRM

A practice CRM with sample data for building, testing and demoing, and the demo tools that make it repeatable.

Every account gets its own sandbox CRM: a stand-in for WelcomeHome, filled with sample communities, sales counselors, prospects and activities. It speaks the same API as the real thing, so anything that works against the sandbox works against your live CRM.

Open it with Open sandbox CRM in the top right of the admin app. There is no separate password: the button signs you in with a link that lasts a few hours.

Warning

Every page carries the banner Sandbox, sample data — a WelcomeHome stand-in for demos and testing. Nothing here is a real person. Nothing you do here touches your real CRM.

What it is for#

Use it toWhy
Build before you connect anythingWrite your playbook and run test calls without touching live records.
Watch what the assistant recordsSee the prospect, the call log and the tour appear as they happen.
Run a repeatable demoReset to the same story every time, and add a contact with your own phone number.
Debug a connection problemThe API log shows every request the assistant made and exactly what came back.
Train new staffLet them hear a call and see what lands, without any risk.

It stays available after you connect your real WelcomeHome account.

The screens#

Contacts#

The prospect list, with search by name, phone or email, and filters for community, stage and status.

Contact detail#

The whole record: residents, influencers with their relationship, do-not-call flags, custom fields, lead source, and a timeline of activities newest first. This is where you watch a call land — the logged call with its summary and the booked tour appear here within moments of hanging up.

There is also an Add a note box, so you can play the part of a sales counselor during a demo.

Calendar#

Week and day views by community and by sales counselor. The fastest way to see the booked slot land — and to see why other slots were not offered.

Activity feed#

Newest activities across the whole sandbox, updating live. Leave it on a second screen during a demo call.

API log#

Every request made to this sandbox: time, method, path, status, duration, and the full request and response bodies when you expand a row. If a booking behaved oddly, this tells you exactly what was sent and what came back.

Setup#

Reference data: communities, counselors, activity types, care types, lead sources, relationships and custom fields. Edit it to match the story you are demoing.

Rooms lists each room's market rate, for a CRM price sync. Change a rate, press Sync now under Pricing in the admin app, publish the change, and a test call quotes the new starting price. A rate can also start on a later date, to try Preview a date. Edits go through the same API the assistant uses, so the UI and the assistant can never disagree.

Demo tools#

Four one-click tools make a demo repeatable.

Reset to sample data

Deletes every contact, activity and setup change in this sandbox and restores the sample data. The API token stays the same, so your connection keeps working.

Run it before every demo and you start from the same story every time.

Add a contact with your phone number

Creates a prospect with your phone number, so when you call the assistant it recognises you and greets you by name.

Fill in a first name and a phone number, pick a community, and choose the relationship to the resident. If you choose anything other than Self, you also give the resident's name, which is how a real family enquiry usually looks.

This is the single most convincing thing you can do in a demo.

Fill or clear a day

Fill day books out every slot on a day so you can show how the assistant handles a full calendar. Clear day frees them all again.

Pick the date and the community; the date is read in that community's time zone.

Slow or failing CRM

Two switches that show the fallback path live.

Slow CRM makes every request wait four seconds — longer than the assistant's tool timeout — so it greets callers without a CRM match and takes a callback instead of booking.

Failing CRM makes every request fail. The assistant keeps the conversation going, captures a callback window and queues the call log to be retried.

Warning

Turn both off when the demo is over. While either is on, the assistant and the platform see a broken CRM, even though these sandbox screens look fine.

A demo that works#

  1. Reset to sample data.
  2. Add a contact with your phone number, as a daughter calling for a parent.
  3. Open the Activity feed on a second screen.
  4. Call your test number. You are greeted by name.
  5. Ask about memory care, then accept a tour time.
  6. Watch the call log and the tour appear in the feed while you are still talking.
  7. Open the contact to show the summary your counselor would read.

Moving to your real CRM#

Nothing carries across. The sandbox and your live WelcomeHome account are separate worlds, and that is the point. When you are ready, add the real connection, set each community's CRM location, point your playbook at it, and publish. See Connect WelcomeHome.