How it works
From a pile of systems to one workspace.
Five steps, in the order they happen. Each one is something you do in the product, not a line in a project plan.
- 1
Start a workspace
Sign in with a one-time link to your work email, or with Microsoft 365. There is no password to choose. Name the workspace and pick the country.
The country sets the currency, the financial year, how a phone number is read and what a receipt says. Each can be changed later in Settings.
Pick the countryCountry Currency Year from Phone Receipt Australia AUD July +61 Australian deductible gift receipt United States USD January +1 United States contribution acknowledgement New Zealand NZD April +64 Plain receipt, no tax claim United Kingdom GBP April +44 Plain receipt, no tax claim Canada CAD January +1 Plain receipt, no tax claim - 2
Switch on modules in your own words
The first screen asks what the company does. Write it the way you would say it. Roost proposes the switches and quotes the phrase behind each one.
You read it, change what is wrong and save. The sidebar you land on is yours, not everybody's.
What Roost proposes- ProgrammesYou said “classes”.
- ShopYou said “shop”.
- Campaigns and journeysYou said “newsletter”.
- 3
Bring your people in
People come in through TellParrot, not a side door. Connect the systems you are leaving, or hand over the spreadsheet. TellParrot matches the duplicates, keeps where every value came from, and delivers one governed record.
What only the old tool knew, who said stop and which list someone was on, is imported into Roost directly, and each import can be undone.
Four systems, one personThe old CRM
Ada Demo
Bookings
A. Demo
Invoicing
Ada Demo-Smith
The spreadsheet
ada demo
Matched by TellParrotOne governed record
Ada Demo
4 sources · lineage kept
- 4
Work the day
The inbox, the bookings, the invoices, the campaign going out on Thursday. Each one reads and writes the same customer, so whoever answers the phone sees the booking and the invoice.
Switch on another module when the business needs it. Nothing already there moves.
Ada Demo · todayLive- 08:40InboxQuestion about Thursday
- 09:15BookingSite visit, confirmed
- 11:00InvoicePaid online, receipt sent
- 14:30CampaignSpring newsletter, scheduled
- 5
Nothing changes quietly
Nobody edits the master record in place. A correction, from a customer in the portal or from staff, goes back to TellParrot as a request. A person reviews it there, and it comes back in the next delivery.
The request closes itself when the new value arrives, and the audit trail keeps who asked and when.
One correction- 01Asked
- 02Sent to TellParrot
- 03Reviewed
- 04Delivered
A local edit would be overwritten by the next delivery and break the lineage. A request does neither.
What stays true
Three rules that do not bend.
One door
People only arrive from TellParrot
Off is not deleted
A switch hides, it does not destroy
Every change
Written down as it happens
Next step
Step one takes a work email.
Name the workspace, pick the country, and say what the company does. Roost proposes the rest for you to read.