Skip to content

Service and sites

Customer emails no longer disappear in a mailbox — they become tickets with an owner.

Service tickets carry statuses, priorities, stages and an owner. A ticket is born from an email, a Messenger message, a website chat, or a public self-service form, and the reply lands back in the same thread. On top of that, there's a register of serviced sites with inspections and SMS reminders.

What it covers

  • Tickets with statuses, priorities, stages and owners
  • A ticket from an email — the reply lands back in the same thread
  • A ticket from Messenger, Instagram, Telegram or the website chat
  • A public self-service form on the website
  • Priorities and deadline control based on stage times
  • Notifications to Microsoft Teams and a daily summary by email
  • An FAQ and knowledge base, a ticket window in the customer portal
  • Site register: inspections with checkpoints, findings, SMS reminders

FAQ

Questions about this area

Did not find your answer? Ask us

How does an email become a ticket?

You point the system at the mailbox whose emails should be evaluated. It recognises whether this is a real request, what its topic and priority are, and creates an incident with an owner. The reply goes back into the same thread.

Is there SLA management?

Partly. There are priorities, stages and stage times, so you see and control deadlines. The system doesn't yet have SLA contracts with automatic escalation — we say this plainly so there's no surprise during rollout.

Can the customer submit a ticket themselves?

They can — through the public form on the website or through the customer portal, where they also see their past tickets.

Who are sites and inspections for?

For cleaning and maintenance services, security, technical maintenance, rentals and repair shops. A site can be a building, a machine, a vehicle or an area.

Start working with Spin CRM today

14 days free, no card required. We will help you migrate your data and train your team.