Skip to main content

​
Survey Delivery

Survey delivery routes collect customer feedback from widget prompts and signed email links. These routes are customer-facing response surfaces, not /api/v1 REST API endpoints authenticated with woesk_ workspace API keys.

​
Feedback Surfaces

​
Widget Survey Responses

Widget survey responses use the active survey definition for the workspace. The survey definition determines whether the score must be:
  • CSAT: 1 to 5.
  • NPS: 0 to 10.
Widget survey routes are scoped to the current widget conversation. They verify the widget key, conversation secret, enabled survey, score range, and workspace relationship before writing a response. They should be called by the installed widget or SDK, not by a server-side REST API integration.

​
Email Survey Responses

Email surveys use signed links generated when Woes sends the survey email. Flow:
  1. An operator or automation sends an enabled email survey.
  2. Woes generates a signed token containing workspace, conversation, survey, score, and expiration data.
  3. The email includes one-click score links.
  4. The customer clicks a score.
  5. Woes verifies the token, expiration, workspace, conversation, survey, and score range.
  6. The response is inserted into support_survey_responses.

​
API Boundary

Use the widget routes for customer browser feedback and the account route for authenticated operator-driven survey sends. Use /api/v1 only for documented server-side integration endpoints.
Email response links are intended for the recipient. Do not expose signed survey links in public docs, tickets, screenshots, or logs.
See Widget Routes and Route Boundaries for the broader security model.
Last modified on July 3, 2026