Audience
Relationship Management.
Members, attendees, donors, or students: one record, with every email, donation, visit and check-in already on it.
Every record type you need. All tied to the people you serve.
Contacts
The people you serve, and their interactions, on one timeline.
Companies
The organizations behind the people: employers, partners and sponsors, linked to their contacts.
Your own record types
Grants, pledges, shifts, cases: record types you define yourself, with your own fields and stages.
Every interaction. On one record, in order.
A contact is not a row, it is a history. Whatever happens in any part of Mercleo lands on the person it happened to, so whoever opens the record next reads the whole relationship.
- Every send, donation, visit and check-in lands on the person it belongs to
- The timeline is the record itself, not an export of it
- Lifecycle stages that move when the relationship does
Not every record fits a template. Build the one you need.
Grants, pledges, memberships, volunteer shifts, cases: define the record type, give it fields and stages, and it behaves like everything built in.
- Your own fields and stages, no developer required
- Linked to the people and companies they belong to
- Reportable like everything built in
When the record changes. It can act on its own.
A workflow watches the record and acts the moment something changes: a stage moves, a gift lands, an engagement threshold is crossed. Set the rule once and every run is logged step by step.
- Triggers on stage changes, gifts and engagement thresholds
- Updates fields, sets stages and logs activities on the record
- Calls a webhook when the change should leave Mercleo
Against your CRM. And the shape it forces on you.
Every CRM is shaped like B2B sales. Your relationships are members, attendees, donors, or students, and the records that matter to you were never something it was built to hold.
| A CRM shaped like B2B sales | Mercleo Audience | |
|---|---|---|
| A supporter fills in your form | A duplicate to merge later | Matched to the person you have |
| A gift comes in | Re-keyed from the payment tool | On the record as it happens |
| Tracking a grant | A spreadsheet beside the CRM | A record type you define yourself |
| Reading the whole relationship | Five tabs in five tools | One timeline, in order |
- Also in Audience
- CSV import with dedupe
- Field mapping
- Custom fields
- Lifecycle stages
- Lists
- Activity timeline
- Companies
- Custom object stages
- Engagement thresholds
- Workflow run logs
- Webhooks
- Passwordless portal sign-in
One record. And your Audience built on it.
Events
Every registration, ticket and check-in lands on the record the moment it happens.
Questions we get asked.
CSV import with field mapping and dedupe. Bring your mess.
Any record type you define yourself: grants, pledges, volunteer shifts, cases, equipment. Your own fields, your own stages, reportable like everything else.
Journeys act on people over time: send, wait, branch. Workflows act on records the moment something changes. The short test: sending something to a person is a journey, changing something on a record is a workflow.
No. A record is yours, not theirs. If they sign in to your portal to hold tickets or receipts, that’s a one-time email code, never a password, and never a seat.
It all works on its own: contacts, custom objects, workflows and reports. Add a module later and it lands on records you already have.