Event to accepted response
Deliver an eligible invitation and accept one valid response.
4 stages · 0 approvals
Roles and responsibilities
-
Step 1Resolve the occurrence
Invitation NumberCampaignChannelScheduled Send AtSMS
-
Step 2Deliver with current preferences
Invitation NumberCampaignChannelScheduled Send AtSMS
-
Step 3Accept valid answers
Response NumberCampaignInstrumentResponded At
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Resolve the occurrence
An authenticated Helpdesk resolution, onboarding/purchase/renewal completion event, quarterly schedule or manual campaign occurrence resolves eligible customers once. Record SourceSystem plus stable event/period identity in OccurrenceKey. Deduplicate by tenant, campaign, customer and occurrence; an always-on campaign may address a later eligible interaction after its frequency cap. Quarterly NPS uses a distinct period occurrence and approved rolling90-day throttle; configured5,000-per-day batches do not change eligibility. Stale CRM or unresolved identity holds Queued work.
Deliver with current preferences
Create Queued invitations with the exact instrument, assigned stable A/B variant, ScheduledSendAt and ExpiresAt. Before every initial send, delayed dispatch, fallback or reminder, recheck active campaign/window, current contact, opt-outs, consent and frequency reservation atomically. A DeliveryAttempts request records the frozen payload and provider key. Accepted provider outcomes set SentAt; timeout remains Unknown and is reconciled with the same request rather than resending. Verified callbacks may record open/bounce, never a response. Reminders reuse the invitation with bounded numbered attempts, stop after a response, and cannot bypass suppression.
Accept valid answers
The response service validates the hashed token, expiry, same campaign/instrument, active response window, allowed question choices/ranges and required visible answers. Accept header, answer rows, private SubmissionReceipts and invitation Responded state atomically. One accepted receipt per invitation; repeated identical command returns its original result, changed payload or replay cannot overwrite accepted answers. Anonymous capture nulls Invitation, Customer and all interaction references on business response/comment rows. Only the private service correlation can join delivery to completion. Staff queries/exports cannot traverse it; anonymous comments are masked and small slices are suppressed.
Retain the observation basis
Keep delivery timestamps, accepted response state and the assigned instrument available to permitted reports. Expired tokens and changed replay payloads remain rejected. A provider open is not a completed response. Anonymous projections exclude private correlation and interaction references, including through exports. Privacy or invalidation actions retain an auditable basis for later recomputation instead of silently changing a dashboard total.
Approvals and exception handling
0 approvals required in this process
- Reserve frequency and dispatch eligibility atomically.
- Reconcile Unknown sends with the original provider request.
- Only accepted submission sets Responded; delivery callbacks cannot.
- Anonymous responses never expose recipient joins or create identifiable outreach.
When the process needs attention
-
hold
Resolve the occurrence
Stale CRM or unresolved identity holds Queued work.
-
reject
Retain the observation basis
Expired tokens and changed replay payloads remain rejected.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Resolve the occurrence | CustomersSurveyCampaignsSurveyInvitations | Queue one eligible invitation per customer and occurrence |
| 2 Deliver with current preferences | SurveyInvitationsDeliveryAttemptsOptOutsSurveyDeliveryRules | Record accepted, suppressed or uncertain delivery |
| 3 Accept valid answers | SurveyResponsesResponseAnswersSubmissionReceipts | Commit one validated response and private receipt |
| 4 Retain the observation basis | SurveyResponsesSurveyInvitationsDeliveryAttempts | Preserve the exact delivery and response population |
Process reports
All reportsParticipation & Response Rate
Per Campaign: invited, sent, opened, responded, suppressed (with SuppressedReason mix), bounced, response rate and days-to-respond distribution. Surfaces deliverability problems and survey fatigue.
Run by an agent
Agent support
Proto cannot approve a self-prepared campaign or follow-up, bypass current consent, expose anonymous recipient correlation, edit accepted responses or declare an A/B winner from sample size alone. Provider outcomes require verified acknowledgments; classification remains a suggestion.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› event to accepted response · resolve the occurrence on Customers, SurveyCampaigns, SurveyInvitations
✓ An authenticated Helpdesk resolution, onboarding/purchase/renewal completion event, quarterly schedule or manual campaign occurrence resolves eligible customers once.
› event to accepted response · deliver with current preferences on SurveyInvitations, DeliveryAttempts, OptOuts, SurveyDeliveryRules
✓ Create Queued invitations with the exact instrument, assigned stable A/B variant, ScheduledSendAt and ExpiresAt.
› event to accepted response · accept valid answers on SurveyResponses, ResponseAnswers, SubmissionReceipts
✓ The response service validates the hashed token, expiry, same campaign/instrument, active response window, allowed question choices/ranges and required visible answers.
› event to accepted response · retain the observation basis on SurveyResponses, SurveyInvitations, DeliveryAttempts
✓ Keep delivery timestamps, accepted response state and the assigned instrument available to permitted reports.
Other processes
3 moreSurvey to approved campaign
Publish the instrument and approve the exact campaign before launch.
4 stages · 1 approval
Low score to reviewed follow-up
Assign attributable customer outreach and independently review the result.
4 stages · 1 approval
Feedback to comparable insight
Combine trustworthy metrics, customer themes and controlled experiments.
4 stages · 0 approvals