AlterCall / Sales engagement / System 06 of 06
2021Recorded work
Tag-based meeting registration
Register the right contact group for a supported meeting and keep the joining link on each contact’s record.
- Noah’s contribution
- Noah documented the selection, registration and maintenance logic.
- Historical stage
- Historical configuration and maintenance walkthrough
- Part of the business
- AlterCall overview ↗
- Make / Integromat
- CRM contacts
- Contact tags
- Meeting platform
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- New meeting
A meeting-created event supplies the name used by the admission filter. - Supported patterns and tag rules
Maintained name patterns and matching tags define the admitted meeting types. - Does the meeting name match?
Only meetings with one of the configured patterns continue into registration. - Leave other meetings out
Unmatched names stop at the filter rather than selecting an audience. - Translate meeting type into a tag
The explicit switch maps a supported meeting-name pattern to its contact tag. - Read the tagged contact audience
List the contacts whose existing profile carries the selected tag. - Register the selected contacts
Register each selected person for the meeting associated with that tag. - Return the meeting link to the profile
Write the useful meeting reference to the registered contact’s record.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Meeting type | Recognizable text within the meeting name and its mapped tag | Select the correct audience rather than registering every contact. |
| Tagged audience | Existing contact records carrying the selected tag | Provide the set of people to register. |
| Contact meeting reference | Stored meeting link | Keep the registration result accessible from the profile. |
Inside the system / 01
Select an audience from an existing customer context
A new meeting needed the relevant contacts registered without someone adding them one by one. Existing contact groups defined the audience; the automation connected each supported meeting type to the right group.
Its first decision was whether the incoming meeting belonged to a supported type. A filter checked recognizable text in the meeting name. Meetings without a supported pattern did not enter the described registration path.
Inside the system / 02
Use one mapping to connect the event and the audience
For a supported meeting, a switch translated the meeting-name pattern into the appropriate tag. The workflow then listed contacts carrying that tag and registered those contacts for the meeting. This kept the selection rule separate from the registration action.
The selection depended on consistent meeting names and maintained contact groups. It used explicit rules linking a known meeting type to a known audience.
Inside the system / 03
Return the useful reference to the contact
After registration, the same meeting link was added to the contact profile. This completed the handoff by preserving a reference alongside the customer record, instead of leaving the result only in an automation execution.
The walkthrough described a small, concrete maintenance procedure. Adding a meeting type required adding its recognizable text and corresponding tag to the mapping, and also including it in the filter. Both parts mattered: selecting a tag alone would not admit an event that the filter still rejected.
Inside the system / 04
A bounded event-operations component
This registration component linked meeting selection, the existing audience and a useful joining reference on the customer record.
The historical configuration included a clear procedure for adding new meeting types. Attendance improvement and complete handling of repeated registrations were not established.
Within AlterCall