• About us
Log inDemo

Surveys · Marketing

Ask when the ticket closes. Read the answer on the client.

From the questionnaire to the follow-up, in five steps.

The questionnaire is written once

Rating, scale, NPS, choice, open text. A branch asks the unhappy respondent why and the happy one for a quote. It is saved as a survey the whole workspace can send.

From the questionnaire to the follow-up, in five steps.

  1. Rating, scale, NPS, choice, open text. A branch asks the unhappy respondent why and the happy one for a quote. It is saved as a survey the whole workspace can send.

  2. Ticket closed, delivery done, event over: a rule on the record sends the survey to the right person, by email, by SMS or as a QR code on the document.

  3. One question per screen, the client's name and the ticket already known, no login. Two taps on a phone, thirty seconds, done.

  4. Not in a results table: on the ticket as a field, on the client as a running score, on the month as a point. Whoever opens the ticket sees the 4.

  5. Under 3 opens a task for the account lead with the comment quoted, on the record, the same day. Over 4 is a line on the client you can point to at the renewal.

The questions, the branch, the reminder, and who answered.

What is asked, what sends it and what happens to a low score are yours to set.

See it on your own data

Every question type you need

Rating 1 to 5, NPS 0 to 10, single and multiple choice, scale, open text, date, file.

A branch, not a wall of questions

A 2 asks what went wrong; a 5 asks for a quote. The respondent sees three questions, never twelve.

Templates that are surveys already

After-ticket rating, post-event, delivery rating, NPS quarter, candidate experience, employee pulse. Copy one, change a question, send.

Who answered, who did not

Sent, opened, answered, per survey and per send, and the response rate read against last month.

One reminder, once

Three days after the send, the people who have not answered get one message. Then it stops.

The same survey, for a business that rates a visit and one that rates an interview.

What adapts: what the survey is about (a visit, a ticket, an application, an event), what sends it, who answers it, how many questions it asks, where the score lands and what a low score opens. Two businesses can run Surveys and disagree on every one of those.

See it on your own data

A cleaning contractor rating every visit

The survey is two questions on the site contact's phone, opened from the QR code on the worksheet the technician just had signed. The score lands on the site, on the team and on the month, and a rating under 3 opens a task for the area manager before the van is back.

A recruitment agency asking every candidate

The survey is six questions, sent by email the day an application reaches Hired or Declined, answered by the candidate. The score lands on the recruiter, on the job and on the quarter, and the client reads the quarter's figure in its review.

The answer on the record.

Léa's 4 is one answer, and it is seen three times. On the ticket it is a field, next to who closed it and when. On Atelier Nord it is the twelfth answer in a score of 4.7, next to the contract and the open quotes. On September's dashboard it is one point in 4.3. Nobody copied it anywhere; the survey knew which ticket sent it.

See it on your own data

On the ticket

Satisfaction is a field on the ticket, so the support lead sorts closed tickets by it and reads the 2s first. See Helpdesk.

On the ticket

On the project

Every answer about a visit or a milestone lands on the project, so the score is read beside the budget and the hours. See Project.

On the project

On the client

The client's score is the answers over time, so the renewal call starts from the last six, not from a feeling. See CRM.

On the client

The score, per client, per team, per month.

Because every answer is on a record, the score is a view on those records, not a chart inside one survey. Per client, to see who is drifting. Per team, to see whose visits are rated lowest. Per month, to see whether the fix worked. The same view across the after-ticket rating, the delivery rating and the post-event survey, saved once and read every Monday.

See it on your own data

What starts a survey.

What is asked, what sends it and what happens to a low score are yours to set.

Book a demo

A rule on any record

When a status changes, when a date passes, when a document is signed: the rule names the record, the survey, the recipient and the wait. One client is never asked twice in a month, because the rule can read the last answer.

The event

The morning after the event's status turns to Over, the attendees get the post-event survey, and the answers land on the event.

The delivery

The delivery note carries a QR code. Scanning it opens the two-question rating, already on the order.

The ticket

Closed means asked, once per client per month at most, and the answer is on the ticket before the support lead reads the queue.

The anniversary of the contract

Eleven months in, the yearly review goes to the client's contact, and the renewal conversation opens on the answer.

A rule on any record

When a status changes, when a date passes, when a document is signed: the rule names the record, the survey, the recipient and the wait. One client is never asked twice in a month, because the rule can read the last answer.

Book a demo

This is the room.

One survey's results: how many were sent, how many answered, the score this month, and every answer as a row with the client, the ticket and the comment, sortable by score so the 2s come first.

See it with your own clients

The survey tool you would otherwise buy keeps the answer in the form.

  • The questionnaire, with a branch

    A spreadsheet
    No
    A survey tool
    Yes
    A suite module
    Yes
    Enobase
    Yes

  • Sent when the ticket closes or the delivery is done

    A spreadsheet
    By hand
    A survey tool
    By integration
    A suite module
    Yes, in its own modules
    Enobase
    Yes, a rule on any record

  • The answer as a field on the ticket, the event, the client

    A spreadsheet
    Typed in
    A survey tool
    Synced to another tool
    A suite module
    Yes
    Enobase
    Yes, the moment it arrives

  • The score per client, per team, per month

    A spreadsheet
    A pivot by hand
    A survey tool
    Per survey
    A suite module
    Yes
    Enobase
    Yes, one saved view across surveys

  • The low score followed up

    A spreadsheet
    No
    A survey tool
    By integration
    A suite module
    Sometimes
    Enobase
    Yes, a task on the record

  • Customers, candidates and employees in one place

    A spreadsheet
    Yes
    A survey tool
    Yes
    A suite module
    Separate modules
    Enobase
    Yes, the same module, another record

  • Response rate and one reminder

    A spreadsheet
    No
    A survey tool
    Yes
    A suite module
    Yes
    Enobase
    Yes

  • Time to live

    A spreadsheet
    A day
    A survey tool
    A day
    A suite module
    Months
    Enobase
    One week
What you needA spreadsheetA survey toolA suite moduleEnobase
The questionnaire, with a branchNoYesYesYes
Sent when the ticket closes or the delivery is doneBy handBy integrationYes, in its own modulesYes, a rule on any record
The answer as a field on the ticket, the event, the clientTyped inSynced to another toolYesYes, the moment it arrives
The score per client, per team, per monthA pivot by handPer surveyYesYes, one saved view across surveys
The low score followed upNoBy integrationSometimesYes, a task on the record
Customers, candidates and employees in one placeYesYesSeparate modulesYes, the same module, another record
Response rate and one reminderNoYesYesYes
Time to liveA dayA dayMonthsOne week

Questions about Surveys

Yes. On its own it is a questionnaire, a link and a results page. Turn Helpdesk on and the closed ticket sends it; turn CRM on and the client carries the score.

EventsThe event whose end sends the survey and whose record keeps the answers.ExploreCRMThe client whose score is read before the renewal call.ExploreHelpdeskThe ticket that asks when it closes, and carries the answer.Explore

See Enobase on your own clients.

Book a demoGet access
Solutions
  • Finance
  • Quotes
  • E-Invoicing
  • HR & Payroll
Industries
  • Catering
  • Construction Company
  • Private Equity
  • All industries
Platform
  • Data Model
  • Knowledge & Collaboration
  • AI & Workflows
  • Analytics
  • Integrations
Company
  • About us
  • Hiring policy
  • Press & Brand
  • Download
  • Privacy
  • Terms
  • Subprocessors

© 2025 Enobase, Inc. All rights reserved.

  • LinkedIn
  • X
  • GitHub
marketing/widget-actions
with Rating, NPS, Choice, Text, Date, File
Open asset editor
marketing/asset-workflow-node
with "Q1 rating · if 3 or less → What went wrong? · else → May we quote you?"
Open asset editor
marketing/widget-contract-library
with After-ticket rating (live), Post-event (live), NPS quarter (draft), Candidate experience (live), Employee pulse (draft
Open asset editor
marketing/asset-stat-card
with "After-ticket rating, September: sent 71 · answered 44 · 62%"
Open asset editor
marketing/asset-activity-list
with Sent 12 Sep 09:00 · Opened 12 Sep 09:41 · Reminder 15 Sep 09:00 · Answered 15 Sep 10:12
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Cleaning contractor · Survey: After-visit rating · About: INT-2026-0102, Maison Berger · Sent when: worksheet signed · Channel: QR code on the worksheet · Questions: 2 · Score on: site, team, month · Under 3: task for the area manager · marked fields: Sent when, Channel, Under 3 props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Recruitment agency · Survey: Candidate experience · About: application, Project lead, Studio Ferrand · Sent when: stage becomes Hired or Declined · Channel: email · Questions: 6, NPS 0 to 10 first · Score on: recruiter, job, quarter · Under 6: read by the account lead · marked fields: About, Respondent, Score on props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/asset-integrations-grid
widget: marketing/asset-integrations-grid family: widget kind: record frame: sticker subject: one answer seen three ways, on the ticket, on the client and on the month, the same value in each move: the answer arriving as a field on the ticket, then folding into the client's score, then into the month's point neighbour: widget-record-three-ways (platform page) · reused; the record is an answer and the three views are the ticket, the client and the month content: answer: Léa Dumont, 4/5, 17 Sep; on the ticket: HD-2026-0421, Satisfaction 4/5; on the client: Atelier Nord, 12 answers, 4.7, last 4/5; on the month: Services, September, 4.3 props: the answer, the three records not: a results table static: no
Open asset editor
marketing/asset-activity-list
with rows Closed by Léa Dumont 14:05 · Survey sent 14:06 · Answered 4/5 16:20
Open asset editor
marketing/widget-budget-drift
with "Satisfaction, PRJ-2026-0139: 3.6 against target 4.5"
Open asset editor
marketing/asset-status-roll
with Atelier Nord, Satisfaction: 5 · 5 · 4 · 5 · 4, 4.7
Open asset editor
marketing/asset-bar-chart-orders
widget: marketing/asset-bar-chart-orders family: widget kind: chart frame: stack subject: one satisfaction score read by client, by team or by month, with the number of answers behind each bar and the lowest one marked move: the scope chip switching from Client to Month, the bars re-sorting and the marked bar staying marked neighbour: asset-bar-chart-orders · same one-measure-by-period shape; the measure is a score with a count behind it, and the scope switches rather than the year content: Satisfaction, September 2026, scope Client: Delcourt & Fils 4.8 (5) · Atelier Nord 4.7 (12) · Delaunay Group 4.5 (9) · Studio Ferrand 4.4 (7) · Maison Berger 3.6 (11, marked) · all clients 4.3 over 44 answers · chips: Client, Team, Month · saved view "Satisfaction, Services" props: the scope, the period, the threshold that marks a bar not: a single survey's results page static: no tags: modules=surveys,helpdesk,crm · categories=marketing,services · capabilities=analytics · industries= · sections=zoom,grid,bento,split · reusable=yes
Open asset editor
marketing/asset-workflow-node
widget: marketing/asset-workflow-node family: widget kind: record frame: stack subject: the rule that sends a survey, read as a definition: the trigger, the condition it checks, the send move: none; the rule is read, not run neighbour: asset-workflow-node · reused; the trigger is a ticket closing and the branch checks the last answer's date content: When: Ticket status becomes Closed · If: client has no answer in the last 30 days → send After-ticket rating to the ticket's contact, remind after 3 days · Else: skip · Active on: Services team props: the trigger, the condition, the survey not: a running automation static: yes
Open asset editor
marketing/asset-status-roll
with Event EVT-2026-0058: Planned · Running · Over · Survey sent 08:00
Open asset editor
marketing/widget-order-details
with SO-2026-0417, Delaunay Group, Delivered 16 Sep, Rating 5/5
Open asset editor
marketing/asset-activity-list
with rows Closed by Léa Dumont 14:05 · Survey sent 14:06 · Answered 4/5 16:20
Open asset editor
marketing/widget-relationship-reminders
with Maison Berger, contract MB-2026 · Yearly review survey 1 Nov · Renewal 1 Dec
Open asset editor
marketing/screen-finance-dashboard
screen: marketing/screen-finance-dashboard family: screen view: list nav: Inbox, AI Assistant, Dashboards, Clients, Tickets, Events, Surveys (active), Projects, Invoices subject: the after-ticket survey's results as three tiles over a grid of answers, each row carrying the record that sent it content: After-ticket rating · tiles: Sent 71, Answered 44 (62%), Score 4.3 · rows: Léa Dumont, Atelier Nord, HD-2026-0421, 4/5, "Quick fix, the invoice took a while", 17 Sep · Maison Berger, INT-2026-0102, 2/5, "The unit on the second floor is still noisy", 16 Sep · Delaunay Group, HD-2026-0433, 5/5, 15 Sep · Studio Ferrand, HD-2026-0429, 4/5, 15 Sep · columns Respondent, Client, Record, Score, Comment, Date · sorted by Score · filter "September, Services" neighbour: screen-finance-dashboard · reused; the tiles are sent, answered and score, and the grid is answers instead of invoices
Open asset editor

© 2026 Enobase, Inc. All rights reserved.

Log in
All systems normal