How it works
TellParrot masters the record. Roost does the work.
Two products with one rule between them: the record of a person is mastered in TellParrot, and Roost never edits it in place. Everything staff and members do in Roost is either their own work, which Roost owns, or a request against the master, which returns the long way round.
Step one · Sources in
Every system you already run, into one governed record.
Your membership system, your mailing tool, your ticketing, your donations, the spreadsheet. TellParrot connects each one, matches the duplicates, scores quality on four dimensions and keeps the lineage of every value.
Membership system
Ada Demo
Mailing tool
ada demo
Event tickets
A. Demo
Donations
Ada Demo-Smith
The spreadsheet
Ada
Someone's inbox
ada.demo@…
One record
Ada Demo
Every spelling matched, every source kept, every change traceable. That is what Roost receives.
- Sources
- 6
- Duplicates
- merged
- Lineage
- kept
Step two · Delivered to Roost
A signed feed, a full snapshot, replayable.
Roost provisions a signed webhook in TellParrot for each kind of record: people, memberships, orders, donations, events, notes, relationships. Each delivery is verified and kept, so a feed can be replayed and a record's history read back.
Feeds
One per kind of record
Merges
When the master merges, Roost follows
Withdrawals
A person withdrawn upstream is gone here
Step three · The work
What Roost owns: what you wrote down, who said stop, what you are asking for.
Notes, tags and follow-ups. Which segment somebody was on and which campaign they got. Every consent decision, with the words. Every ask, pledge and gift. Attendance at every session. None of that is master data, and all of it is Roost's.
Step four · Corrections out
A change never happens in place.
A member asks for a correction, or a staff member takes one down on the phone. Roost records the request and pushes it to TellParrot, where a steward reviews it. If accepted, the master changes with lineage, and the next delivery brings the value back.
01
A member asks
Ada changes her postcode in the portal. Nothing on her record changes.
02
Roost records a request
The correction is written down with who asked and when, and sent to TellParrot.
03
A person reviews it
In TellParrot's queue, a steward accepts it. The master changes, with lineage.
04
The value comes back
The next delivery carries it. Roost shows the new postcode, and where it came from.
Step five · Out the door
When data leaves, it leaves under a decision made here.
A mailing audience kept in step with a segment. A campaign that checks consent per person at the moment of sending. An export only a role that may export can take, and every one recorded. A board pack that says where its numbers came from.
Next step
Bring one messy source. Leave with one record.
Connect a TellParrot tenant, add the first feed, and watch a person arrive with their history intact.