Survey Link
Survey Link allows you to create custom URLs to collect feedback from your customers. Simply generate a link with the desired parameters and send it through any channel: email, SMS, WhatsApp, QR Code, receipt, etc.
Endpoint
Base URL: https://survey-link.solucx.com.br/link/{api_token}/
The api_token is your SoluCX instance token. You can find it under Instance Settings in the platform.
How It Works
- Build the URL with the desired parameters
- Send the link to the customer through the channel of your choice
- The customer clicks the link and is directed to the survey
- The response is automatically recorded in the platform
Important: To automatically create a new customer, the link must contain at least name or customer_id.
Available Parameters
Transaction Identification
Use these parameters when you want to link the survey to an existing transaction.
Transaction Parameters
Customer Data
If no transaction ID is provided, the system will create a new transaction. For this, customer identification is required.
Customer Parameters
name is not provided. customer_id is not provided. Transaction and Employee Data
Transaction Parameters
store_name. employee_name. param_orderId, param_serviceChannel). This data is available for analysis, cross-referencing, and clustering within the platform. Warning: Use camelCase after the param_ prefix (e.g.: param_orderId). Do not use snake_case (e.g.: param_order_id), as the system interprets the underscore as a separator.
Advanced Configuration Parameters
Configuration Parameters
email. Accepted values: email, sms, whatsapp, widget, qrcode, tablet, ura, facebook, gmb, api, employee, push_notification, chatbot, workplace, portals. widget, redirects to the compact version of the survey. pt, en, es). Usage Examples
Simple Link with External Transaction ID
When you already have a registered transaction and want to send the survey:
Link with Customer and Transaction Creation
Automatically creates the customer and transaction with the provided data:
Link Specifying Journey and Employee
Directs to a specific journey and links to the employee:
Link with SoluCX Internal ID
When you have the internal transaction ID in SoluCX:
Link with Custom Parameters
Enriches the transaction with additional data for analysis and cross-referencing:
Complete Link with Multiple Parameters
Example combining customer, transaction, employee, and custom parameters:
Link with Specific Form
For Flex Survey journey types that require a form:
Real-World Applications and Use Cases
Generic QR Code (Counter or Restroom)
Ideal for physical locations where you want to capture spontaneous feedback without individually identifying the customer.
Scenario: A QR Code sticker on a shopping mall restroom mirror or a bank branch service counter. A static link is created with a generic name.
Example URL:
Result: The system creates a transaction for the customer "Visitor" linked to the "MallSouth" store in the cleaning journey.
Post-Service Link (WhatsApp/Chat)
Used to close a human service interaction, where the agent sends the link to evaluate the interaction.
Scenario: At the end of a WhatsApp support session, the agent pastes a link. The service system (CRM/Chatbot) generates the link by injecting the customer name and agent name.
Example URL:
Receipt (Dynamic Printing)
The most data-rich case, where each sale generates a unique link printed at the bottom of the receipt.
Scenario: The customer receives the receipt with a QR Code and a call to action: "Scan and rate your $150.00 purchase at the Downtown store." The POS system (ERP) dynamically generates the link for each sale.
Example URL:
Advantage: Allows you to track exactly which register (POS), which store, and which sale amount generated the review, cross-referencing financial data with NPS.
Email Signature
To continuously collect relationship feedback through corporate email exchanges.
Scenario: Footer of an account manager's email. A fixed link in the email signature.
Example URL:
Self-Service Kiosk
To capture feedback at self-service kiosks in stores, airports, or hospitals.
Scenario: After the customer completes an operation at the kiosk (check-in, payment, inquiry), the system displays a QR Code for evaluation.
Example URL:
Notes
- The link can be sent through any channel: email, SMS, WhatsApp, QR Code, etc.
- There is no authentication via header, only via token in the URL.
- If the store or employee doesn't exist, the system tries to create them automatically using
store_nameoremployee_name. - Invalid parameters (such as malformed email or phone outside the standard format) return HTTP 400 error.