AlterCall / Sales visibility / System 05 of 06
2021Recorded work
Setter end-of-day reporting
Collect each appointment setter’s daily activity, appointment details and ratings, then file and share their report.
- Noah’s contribution
- Noah configured the form distribution, response aggregation and Monday/Slack handoffs.
- Historical stage
- Configured workflow, form examples and narrated maintenance changes
- Part of the business
- AlterCall overview ↗
- Typeform
- Slack
- Monday.com
- Make / Integromat
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.
- Daily distribution schedule
The configured late-afternoon run sends reports on working days except Sunday. - Monday setter groups
Named board groups define the setters expected in the distribution run. - Slack user directory
Slack identity data provides the message destination for each matching setter. - Match the setter identity
Compare group and Slack names and pass only matching people. - Send the personalized Typeform
A Slack link carries custom user context into the daily form. - Setter completes the conditional form
Appointment counts choose which names and quality-rating questions are shown. - Retrieve response and form structure
Use question titles to identify and extract the repeated appointment answers. - Aggregate appointment names
Collect the reported appointment names into the daily report context. - Average supplied quality ratings
Calculate the average of the setter’s human ratings for the appointments. - Resolve the Monday group
The maintained matching rule also accommodates a first name in the form response. - Create the setter’s daily item
Store the combined response under the matching person’s board group. - Notify Slack with the answers
Post completion and the associated form answers to the reporting channel.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Personalized form link | Hidden user context and identifying parameters | Associate the report with the intended setter. |
| Daily response | Conversation/appointment information, names and supplied quality ratings | Capture the context behind a daily total. |
| Monday report item | Matched setter group, aggregated names and average rating | Keep the response in the team’s operating workspace. |
Inside the system / 01
A reporting habit needs a reliable handoff
AlterCall’s appointment setters needed a repeatable way to report their day. The configured distribution scenario ran in the late afternoon on working days except Sunday. It listed the groups in the setter-performance board, compared those names with Slack users and sent the matched person a form link.
The personalized link carried the setter’s identity into the form, which could greet them by name and retain that context for filing the response.
Inside the system / 02
Collect the detail that makes a total useful
The form showed appointment-name and quality-rating questions according to the reported appointment count. This kept the request relevant to the person’s day. The recorded form supported a defined maximum number of appointments.
The ratings came from people filling out the form. The automation could calculate an average of those responses, but it did not independently judge a setter’s quality or the quality of an appointment. The appointment names preserved supporting context alongside the numerical summary.
Inside the system / 03
Resolve the destination and preserve the answers
On submission, the response-processing scenario retrieved the response and the form structure. The structure supplied question titles needed to extract the repeated appointment information. One branch collected appointment names and another calculated the average rating before the combined result moved onward.
The workflow then listed Monday groups and selected the relevant person’s group. A maintenance walkthrough changed matching to accommodate respondents who entered a first name rather than a full name. The resulting item went under that group, while Slack received a completion notification and the associated answers.
Inside the system / 04
Make the simplifications explicit
The handler retrieved the latest response, which made testing easier but left overlapping submissions and ambiguous name matches unresolved in the recorded version.
Noah also simplified questions that requested both a count and the same list of outcomes. The work combined form design, distribution and a clear reporting handoff; the ratings remained self-reported, and improved reporting compliance was not measured.
Within AlterCall