Skip to the page
Roost
Start your workspace
Menu

One workspace for the whole company

Replace the pile of systems with one workspace.

Your website, customers, forms, inbox, campaigns, memberships and shop, in one place and on one customer record. Every module is a switch. The record underneath is governed by TellParrot.

Start your workspaceSee how it works
  • No passwords
  • Microsoft 365 sign-in
  • Runs on Microsoft Azure
  • Data stays in your region

  • 22

    Modules, each a switch

  • 9

    Parts that are always on

  • 1

    Record per customer

  • 0

    Passwords to forget

The pile

Ten systems. Ten versions of the same customer.

A website builder, a CRM, a booking tool, invoicing, forms, a phone system, a shared inbox, social scheduling, a newsletter tool, memberships. Each one is fine on its own. None of them agree on who a customer is, so the person who unsubscribed in one still hears from another.

Website

J. Demo

contact form, no phone

CRM

Jordan Demo

old mobile number

Bookings

Jordan D.

booked twice

Invoices

Demo Builders Pty Ltd

billing contact only

Forms

jordan demo

a new person, again

Phone

0400 000 000

unknown number

Inbox

jordan@demo-builders.example

in one person's mail

Social

@jordan.demo

a handle, not a name

Newsletter

JORDAN DEMO

unsubscribed here only

Memberships

Jordan Demo-Lee

renewed under a new name

One Roost recordGoverned

Jordan Demo

Email
jordan@demo-builders.example
Phone
0400 000 000
Company
Demo Builders
Consent
Email no, honoured in every send

10 sources · matched · lineage kept

Every module a switch

22 modules. Switch on what you use.

A module that is off leaves the sidebar, refuses its screens and takes its public pages down with it. Describe what you do in your own words and Roost proposes the switches, quoting the phrase that decided each one. A person reads it and saves.

Data

Who and what you keep records of

  • Peopleoff
  • Master dataoff

Reach

How people find you and hear from you

  • Campaigns and journeyson
  • Forms and surveyson
  • Websiteon
  • Stories and requestsoff
  • Conversationson
  • Playoff

Money

What comes in, and what it is for

  • Fundraisingoff
  • Cheque depositsoff
  • Gift creditsoff
  • Workplace giving and partnersoff
  • Membershipson
  • Shopon
  • Local businessesoff
  • Money by areaon
  • Grantsoff

Delivery

What you run, and who turns up

  • Eventson
  • Programmesoff
  • Volunteersoff
  • Office and agentsoff
  • Riskoff
Always onPeopleNotesSegmentsInboxConsentPaymentsFeedsAudit trailTeam
Every module, explained

A working day

From the first message to the last send, one workspace.

The same customer, the same record, all day. Nobody copies a name from one screen to another.

  1. 08:10 · Conversations

    Jordan Demo

    Could you come Thursday instead?

    You

    Thursday at nine works. See you then.

    On Jordan's timeline

    A customer writes in. The reply goes from the shared inbox and lands on their record.

  2. 09:30 · AppointmentsLabs

    Mon

    Tue

    Wed

    Thu

    9:00 Quote visit

    Fri

    Booked from your public page, with a reminder before and a follow-up if nobody shows.

  3. 11:45 · InvoicesLabs
    INV-0042Demo Builders

    Site visit$180.00

    Materials and labour$1,300.00

    Total$1,480.00

    Paid online · receipt sent

    An invoice with lines and a due date, paid online, with the receipt sent for you.

  4. 14:20 · Forms

    Namejordan demo

    Emailjordan@demo…

    Jordan Demo

    Matched by email · one correction raised

    A form comes in. Someone on file is matched by email; a change they typed becomes a correction, never an overwrite.

  5. 16:30 · Campaigns
    • Ada Demosend · email yes
    • Jordan Demoskip · said no to email
    • Sam Demosend · email yes
    • Lee Demosend · email yes

    3 sending · 1 skipped, and why

    Consent is checked for every person at the moment of sending, not once for the list.

LabsFinished enough to use and not yet the default: an admin switches it on until its date comes round.

Governed by TellParrot · the record is mastered upstream

Governed by TellParrot

The record is mastered upstream. Roost does the work.

Roost is built by TellParrot, the master data and governance platform underneath it. TellParrot matches the duplicates, scores the quality and keeps the lineage. Roost receives that record and gives your team something to do with it.

Mastered upstream

One golden record per customer

Every source is matched in TellParrot, so the record Roost shows is the one your auditor can trust.

Never edited in place

Changes go back as requests

A correction is written down with who asked and when, reviewed by a person, and returns with the next delivery.

Lineage

Every value carries its source

Each value arrives with where it came from, and the master keeps every change to it.

Consent

Checked at the moment of sending

Each channel is its own yes or no, with the exact words agreed to, honoured in every send.

The whole path, from source system to customer portal

Who it is for

One product for every company. Set up for yours.

The same workspace underneath, switched on for the way your kind of company works.

Security

No passwords. Nothing changes quietly.

The same discipline as the record underneath: every action checked, every change written down.

No passwords

Staff sign in with a one-time link or their Microsoft 365 account. There is nothing to leak or reuse.

One permission matrix

Every action checks a capability from one matrix, and staff can be scoped to their own sites.

An audit trail

Who did what, and when, recorded as it happens. The master record keeps where every value came from.

Keys encrypted at rest

Provider keys and feed secrets are encrypted, so a database read alone never yields a live secret.

The security page

Next step

Start with the company you already have.

Sign in with a work email or Microsoft 365, name the organisation, pick a country and switch on the modules you use. Your team joins by invitation.

Start your workspaceSee how it works