Launched: 50 places at launch prices, until 31 December 2026. About the places ›

Signed in

31 file services in 8 countries · 34,000+ ECU files handled

Free to start: no monthly fee

Sign in Your account Help

TunerEngine

Secure checkout: the card is checked by Stripe

Start my portal

    A function of your portal, in full

    The right person hears about every job, message and payment

    Every new file, customer message and payment in your portal becomes a notice, and you decide who gets it and by which way: email, the bell in the portal, a sound, a push or Telegram. A waiting customer reaches a person quickly, and nobody on the team is buried in notices that are not theirs.

    A file portal is only as fast as the moment somebody notices. A customer uploads a read; a tuner has to hear. The tuner delivers; the customer has to hear. Money arrives; the job can go ahead. The portal turns each of these into a notice and sends it down the ways you allow: an email, the bell at the top of the portal, a short sound in the open browser, a push to a browser or phone, and Telegram. Customer conversations have a further way of their own, the Messages app on the team's phones, which is described with the inbox.

    Three sections of Settings, all under Messages and notifications, hold the rules. Email decides how mail leaves the portal, from which address, and who is spared it. Who is told what decides which staff hear about a new job or a new message, which way each kind of notice travels, and whether a monthly report is sent. Sounds gives each kind of event its own note and one volume.

    The rules are built so that silence is never an accident. The emails a person must get, a sign-in code, a password reset, a receipt, an invoice, a security notice, go whatever you switch off. A notice held back from email stays on the bell. A push that is not allowed still leaves its notice in the portal.

    A shop's day without it

    Without it, the shop finds out by looking. Somebody keeps a browser tab open and refreshes it; the rest are told on WhatsApp or by a shout across the workshop. A rush file sits for forty minutes behind the map editor. Or the opposite: every upload emails nine people, the bookkeeper and the owner on holiday included, until nobody reads any of it and the one notice that mattered is lost among the others.

    One new job, and every way it can reach a person.

    A customer uploads a read. This is the road the notice takes, with the rule that opens or shuts each way.

    1. Who is toldThe staff who can take the job, or all staff, as you chose. A job that arrives already assigned by your assignment rules always tells the tuner holding it.
    2. The bellThe notice is on the bell at the top of the portal. A notice held back from any other way still stays here.
    3. A soundIn every open portal page, the note for jobs, at the one volume you set. Nothing plays when the browser is closed.
    4. EmailFrom your own address, while notice emails are on, the person's role is not muted and they are under the hourly ceiling. Past the ceiling the notice is not emailed later; it stays on the bell.
    5. PushTo the browsers and phones that allowed it, even with the portal closed, through your own OneSignal account, when the kind is ticked and its push switch is on.
    6. TelegramWhere the kind can use it and its switch is on. Customer conversations have a further way of their own, the Messages app on the team's phones, described with the inbox.

    Each way has a switch for each kind of notice, on the notification channels page. Only the ways a kind can really use are offered.

    Away from the screen

    The portal is closed, and the tuner still hears.

    With push connected, a notice reaches the phones that allowed it while the portal is shut. Opened, the portal's bell holds everything that arrived, whichever ways were switched off.

    Brackenford PerformanceNew job: Golf 2.0 TDI, Stage 1
    now
    Notifications2 unread
    • JobNew request: Golf 2.0 TDI, Stage 1now
    • PaymentA customer bought credits8 min
    • MessageA customer wrote on a job you hold25 min
    • PeopleA new customer registered1 h
    Drawn from the portal; a sample shop.
    1. Push through your own accountYou make an app in your own OneSignal account and paste its app ID and key. Without both, nothing is sent and the portal's log says why.
    2. Only the kinds worth a buzzTick the kinds sent as push and only those go. It is a second gate beside the push switches on the notification channels page: a push goes only when both allow it.
    3. The bell keeps what the phone missedA push that is not allowed still leaves its notice in the portal, and so does an email past the ceiling or one muted for a role.
    4. Not the Messages appPush here is separate from the Messages app on the team's phones, which belongs to the inbox and rings about customer conversations by itself.

    What goes out whatever you switch off.

    Quietening a portal must never cost somebody a way in or a document they are owed. An email takes this road before it leaves.

    1. Is it one a person must get?A sign-in code, a password reset, a receipt, an invoice, a security notice: it goes, whatever the switches, the muted roles and the count say.
    2. Are notice emails on?Off, every other notice email stops, and the same notices still arrive on the bell, on Telegram and by push.
    3. Is the role muted, or the person?People in the roles you tick never get notice emails, and one person can turn their own off in their own settings.
    4. Is the hour full?Each address has a ceiling on notice emails in one hour, thirty as the portal comes. The next hour starts a fresh count.
    5. It is sentThrough your own mail server, the server the portal runs on, or your Brevo account, from the name and address your customers know.

    What you find on it

    Email

    Settings → Messages and notifications → Email. This section decides how email leaves the portal: through your own mail server, through the server the portal runs on, or through your Brevo account, with the server details that go with the choice. It also holds the sender name and address your customers see, the main switch for notice emails, a ceiling on emails to one person in an hour, the roles that get no notice emails, and whether internal alerts are emailed to staff.

    Its settings, one by one (12) ›

    Who is told what

    Settings → Messages and notifications → Who is told what. Here you choose which staff hear about a new job and about a new message on a job, open the page that switches each way on or off for each kind of notice, connect push through your own OneSignal account, narrow push to certain kinds, and switch on the monthly report for administrators.

    Its settings, one by one (8) ›

    Sounds

    Settings → Messages and notifications → Sounds. One main switch, one volume and five kinds of sound: jobs, payments, people, problems and support chats. Each kind has a note of its own, so a tuner knows a payment from a fault without looking up. The sounds play in open portal pages only.

    Its settings, one by one (7) ›

    How it works

    1. Open Settings, then Messages and notifications, then Email. Choose how email is sent; for your own mail server, fill in the server, port, security, user name and password your provider gives you. The setup wizard fills them for the well-known providers and tries them before anything is kept.
    2. Set the address and the name your emails come from, on the same domain as the mail server, and send yourself a test.
    3. Open Who is told what. Leave new jobs with the staff who can take them and new messages with the people on the job, unless the team is very small.
    4. Leave every way on at first. When one kind of notice annoys, open the notification channels page and switch off that one way for that one kind.
    5. Open Sounds and set the volume for the room the portal lives in. Switch off the kinds nobody acts on; keep the one for problems.
    6. If the team is often away from the screen, connect push: make an app in your own OneSignal account, paste its app ID and key under Browser push notices, and tick the kinds worth a buzz.
    7. After a week, ask the team what they ignore. Mute email for the roles that live in the portal, lower the hourly ceiling, or narrow push, one rule at a time.

    Who it is for

    • The ownerHears the money come in and the faults go wrong without reading every step of every job, and gets the month's figures by email on the 1st.
    • Your tunersIs told about the jobs they can take and the customers they are working for, by a sound at the desk and a push when the browser is closed, and is spared the emails when the tuner role is muted.
    • Your teamAdmins get the internal alerts and the monthly report; anyone whose role is muted keeps the bell and loses only the emails.
    • Your customersGets an email from an address they recognise when the file is ready, and always gets a sign-in code, a receipt or an invoice.

    Every setting, explained

    Email

    12 settings

    Settings → Messages and notifications → Email. This section decides how email leaves the portal: through your own mail server, through the server the portal runs on, or through your Brevo account, with the server details that go with the choice. It also holds the sender name and address your customers see, the main switch for notice emails, a ceiling on emails to one person in an hour, the roles that get no notice emails, and whether internal alerts are emailed to staff.

    Most emails to one person an hour

    A ceiling on the notice emails sent to each address within one hour. A notice past the ceiling is not emailed later; it stays on the bell in the portal, and the next hour starts a fresh count. Receipts, invoices, sign-in codes, password resets and security notices go whatever the count. Zero means no ceiling.

    How it comes
    Thirty.
    When to change it
    Lower it when staff say the portal floods their inbox. Raise it, or set zero, in a shop that reads everything by email and handles few files. Most shops never touch it.
    For example
    A dealer uploads forty files in a morning. The tuner gets the first emails, then finds the rest on the bell.

    Notice emails

    The main switch of the portal's email. On, people are emailed every notice whose way includes email: a new job, a delivered file, a message, a payment. Off, those stop, while the notices still arrive on the bell, on Telegram and by push. The emails a person must get still go when it is off: a password reset, a sign-in code, a receipt, an invoice, a security notice. The hourly ceiling, the muted roles and the system alerts count only while it is on.

    How it comes
    On.
    When to change it
    Leave it on: customers expect an email when a file is ready. Switch it off only while your mail server is being changed. To silence the tuners and not the customers, use Roles that get no notice emails.
    For example
    A shop moving its mailbox to a new provider switches it off for the afternoon; sign-in codes keep going.

    System alert emails to staff

    Some notices are about the portal itself, such as a file that could not be locked again for its tool. They always show in the portal and on Telegram; this adds an email to every administrator. The hourly ceiling applies to them. A customer waiting for approval is emailed to staff whatever this says.

    How it comes
    Off: one failing file can alert every administrator at once, and by email that soon becomes noise.
    When to change it
    Switch it on when nobody watches the portal after hours and a failed file at night must be seen by morning.
    For example
    A delivered file fails to lock for the customer's tool at nine in the evening; the admin sees the email at home and fixes it before the customer rings.

    Mail server security

    The kind of secure connection your mail server expects. The wrong choice is the usual reason a test email never arrives.

    • TLS The usual choice today, on the standard port. If your provider says STARTTLS, pick this.
    • SSL The older way, on its own port; common with the mail of a web host such as cPanel or Plesk.
    • None No secure connection. Only for a server inside your own network that refuses both; the mail then travels unprotected.
    How it comes
    TLS.
    When to change it
    Set it when you connect the server and change it only when the provider changes its instructions.
    For example
    Gmail and Microsoft both use TLS on the standard port.

    Emails come from

    The sender address on every email the portal sends: notices, invoices, sign-in codes. Replies go to this address, in your normal mailbox; the portal does not read them. It should sit on the same domain as the mail server you connected, or many providers refuse to send.

    How it comes
    Empty. While email goes through this server, the mail still carries your portal's name.
    When to change it
    Set it on day one, before the first customer. Change it when you change domain or mailbox, and change the mail server with it so the two agree.
    For example
    files@ the shop's own domain: an address customers know and can reply to, not one they leave in spam.

    Sender name

    The name inboxes show beside that address. It appears on the email that carries an invoice, not on the invoice itself, which takes its details from the invoice settings.

    How it comes
    Empty: the portal's name is used.
    When to change it
    Leave it empty unless the business name differs from the portal's name. A business name reads better than a person's, since every email from every tuner carries it.
    For example
    "Northgate Remaps files desk"

    Mail server

    The address of your provider's outgoing mail server, such as smtp.yourdomain.com. The setup wizard fills it in for Gmail and Google Workspace, Microsoft, Zoho, SendGrid, Mailgun, Postmark and Amazon SES, and tries it with the other details before anything is kept. It is ignored while email goes through this server or Brevo.

    How it comes
    Empty.
    When to change it
    Set it when you choose your own mail server, and change it when you move provider. If the portal says it cannot reach the server, check the address for a typo, then the port and the security.
    For example
    A shop on a web host with cPanel uses mail.yourdomain.com, with its mailbox and that mailbox's password.

    How email is sent

    The way every notice, invoice and sign-in code leaves the portal. The choice decides which of the mail settings under it matter, and shows or hides them to match.

    • Your mail server (SMTP) Mail from your own domain through the provider you already have: Gmail, Microsoft, Zoho, your web host and others. The way inboxes trust most.
    • This server The portal sends from the server it runs on. Nothing to set up; fine for a start or a test.
    • Brevo For a shop that already sends its mail with Brevo: one key, pasted in the password field, instead of server details.
    How it comes
    Your mail server.
    When to change it
    Use your own mail server as soon as you have one: it is what makes your emails look like yours and land in the inbox. Use this server to get going. You can switch later without losing anything; only the road changes.
    For example
    A new shop starts on this server for its first week, then connects the mailbox on its own domain before inviting customers.

    Mail server password

    The password for that user name, or your Brevo API key when email goes through Brevo. It is kept as a secret, shown as dots once saved, and never written on a page or in an email. Only an owner or admin can replace it.

    How it comes
    Empty.
    When to change it
    Change it whenever the mailbox password changes; otherwise the portal's emails stop quietly. A test email tells you at once.
    For example
    Gmail refuses the everyday password: it wants an app password, made in the Google account under Security.

    Mail server port

    The port the portal connects to on that server: usually 587, or 465 for SSL. On the SSL port the portal connects the SSL way whatever the security choice says.

    How it comes
    587.
    When to change it
    Leave it unless your provider says otherwise. If a test email fails, check this and the security choice together.
    For example
    A web host that offers only the SSL port: the shop sets 465 and picks SSL.

    Mail server user name

    Who the portal says it is when it signs in to your mail server. For most providers it is the full email address of the mailbox; a few give a fixed user name, and the setup wizard says which.

    How it comes
    Empty.
    When to change it
    Set it with the server. When you send from a different mailbox, change it together with the password and the sender address.
    For example
    An owner types only the part before the at sign and the server refuses the sign-in; the whole address fixes it.

    Roles that get no notice emails

    People in the roles you tick, customers, tuners or admins, get their notices in the portal, on Telegram and by push as before, and never by email. What a person must get, such as a sign-in code or an invoice, is still sent. One person, as opposed to a role, can turn their own email notices off in their own settings.

    How it comes
    No role is muted.
    When to change it
    Tick the tuners when the team works inside the portal and the emails are only noise. Leave customers unmuted: the email that says a file is ready is the one they wait for.
    For example
    The tuners ask for the emails to stop. The owner mutes their role, and customers go on hearing about every delivery.

    Who is told what

    8 settings

    Settings → Messages and notifications → Who is told what. Here you choose which staff hear about a new job and about a new message on a job, open the page that switches each way on or off for each kind of notice, connect push through your own OneSignal account, narrow push to certain kinds, and switch on the monthly report for administrators.

    Who hears about a new message

    The staff told when a customer writes on a job. The person who wrote is never told about their own message, and anybody who may work the job can still open it and step in.

    • The people on the job The assigned tuner, the customer, anyone already in the conversation and, only while nobody has taken the job, the staff who could.
    • All staff Everybody on staff, on every message.
    How it comes
    The people on the job.
    When to change it
    Keep it for any team of more than two. Choose all staff only when everybody really answers every customer and the volume is small.
    For example
    One job with twenty messages no longer wakes six people for every line.

    Monthly report by email

    On the first morning of the month, every administrator gets one email about the month that has just ended: jobs received, jobs finished, money taken through credit purchases and new customers, each set against the month before, with the number of customers in all. The same report is left on the bell. Jobs paid in other ways count as jobs, not as money. Tuners and dealers do not get it.

    How it comes
    Off.
    When to change it
    Switch it on once the portal has a month of real work behind it; before that the comparison says little.
    For example
    An owner who never finds the hour to look at the figures sees a quiet month on the 1st, not on the bank statement a quarter later.

    Who hears about a new job

    The staff told when a customer sends a new request. It decides who is interrupted, not who can see: the queue still shows every open job to everyone who may work it. A job that arrives already assigned by your assignment rules always tells the tuner holding it.

    • Staff who can take it The tuners and others whose role may claim a job, and nobody else.
    • All staff Every member of staff who can be notified.
    How it comes
    Staff who can take it.
    When to change it
    Keep it. Widen it to all staff when an owner or admin who does not tune still wants to see each upload the moment it lands.
    For example
    Every upload used to ring nine people; by the afternoon nobody looked. Now it rings the three who tune.

    Which way each notice is sent

    Opens the notification channels page: every kind of notice the portal sends, grouped, with who receives it and a switch for each way it can travel, email, the portal, push or Telegram. Only the ways a kind can really use are offered. The page links to each notice's template, so the road and the words sit side by side.

    How it comes
    Every switch on, so a portal that never opened the page behaves as before.
    When to change it
    Come back when one kind of notice annoys, and turn off one way for that one kind. The switches for all email and all push are elsewhere, and blunter.
    For example
    A shop wants payments by email and Telegram but messages only inside the portal, and sets exactly that.

    Notices sent by push

    The kinds of notice sent as push. With nothing ticked, every kind is sent; once any are ticked, only those go. It is a second gate beside the push switches on the notification channels page: a push goes only when both allow it. Email, the bell and Telegram are untouched.

    How it comes
    Nothing ticked: every kind is pushed.
    When to change it
    Leave it empty to begin with. Once you know which buzzes the team acts on, tick only those. To stop push entirely, switch off Browser push notices.
    For example
    A shop ticks new jobs and payments; the small steps of each job stop buzzing phones.

    OneSignal app ID

    The ID of your app in the OneSignal dashboard, put on every push the portal sends. It is not a secret; the key beside it is. It shows only while Browser push notices is on.

    How it comes
    Empty.
    When to change it
    Set it when you connect push; change it only if you make a new app in OneSignal.
    For example
    Push is on and the key is pasted, yet nothing arrives: the app ID was never filled in.

    Browser push notices

    Sends notices as push to the browsers and phones that allowed them, even when the portal is closed, through a OneSignal account you hold. It needs the app ID and the key under it; without both, nothing is sent and the portal's log says why. It is separate from the Messages app on the team's phones, which belongs to the inbox and rings about customer conversations by itself.

    How it comes
    Off.
    When to change it
    Switch it on when the team is not always in the portal and jobs must be seen at once. Leave it off while Telegram already does that for you.
    For example
    A tuner closes the browser at lunch; the rush job that lands reaches his phone anyway.

    OneSignal key

    The REST API key of that app, which proves to OneSignal that the portal may send for it. It is the app's key, not a user key. It is kept as a secret and shown as dots once saved.

    How it comes
    Empty.
    When to change it
    Replace it if you make a new key in OneSignal or think the old one has leaked. To check it, trigger a notice of a kind you send by push and watch the browser.
    For example
    A shop pastes a user key by mistake; the log names OneSignal's refusal, and the app's own key puts it right.

    Sounds

    7 settings

    Settings → Messages and notifications → Sounds. One main switch, one volume and five kinds of sound: jobs, payments, people, problems and support chats. Each kind has a note of its own, so a tuner knows a payment from a fault without looking up. The sounds play in open portal pages only.

    Notification sounds

    Plays a short sound in every open portal page when a notice arrives, for each kind left on under it. Off, it silences every kind at once. A customer with their page open hears the kinds that apply to them, such as a message. Nothing plays when the browser is closed; that is the job of push, or of the Messages app described with the inbox.

    How it comes
    On.
    When to change it
    Leave it on where the portal sits open on a workshop screen. In a quiet office, switch off single kinds before you switch off everything.
    For example
    The job list is open behind the map editor; the tuner hears the rush file land and switches tabs.

    Sound for jobs

    The sound about work: a job arrives, moves to another step or is finished. A customer's message on the job is not this kind; that is Sound for people.

    How it comes
    On.
    When to change it
    Keep it where jobs must be seen at once. Switch it off in a shop that handles hundreds of files a day, where it would never stop.
    For example
    An owner keeps the payment sound and drops this one, so the room is quiet until money lands.

    Sound for payments

    The sound when money comes in: credits bought, a file paid for. Its note differs from the job note, so you can tell the two apart without looking.

    How it comes
    On.
    When to change it
    Keep it: it is the sound that says a waiting job can go ahead. Switch it off only where payments arrive so often the sound is constant.
    For example
    A tuner hears the payment for a job on hold and starts it before the customer has finished typing.

    Sound for people

    The note for a person: a customer writes, replies or mentions you, or somebody signs up. Off, those notices still arrive on the bell and as a pop-up, without the sound.

    How it comes
    On.
    When to change it
    Leave it on in a shop where messages come in all day. Turn it off where the only sounds you want are a new file and a payment.
    For example
    A customer writes three times asking which gearbox option to pick; the owner at the bench hears the first.

    Sound for problems

    A falling note, unlike any other in the portal, when a notice says something failed, was rejected or declined, expired or went overdue: a delivery that did not go, a payment the bank refused, a file sent back. The pop-up and the bell name the job or the payment and open it.

    How it comes
    On.
    When to change it
    Keep it even in a shop that turns the others off: a fault that is heard is fixed in a minute. Turn it off only on a screen nobody sits at.
    For example
    A delivery fails at six in the evening and the tuner hears it before leaving, not from the customer the next morning.

    Sound for support chats

    A quick rising triple when a chat needs a person now: a customer asks for help, the assistant hands a conversation to your team, or a reminder says a customer has waited too long. The assistant's own answers make no sound.

    How it comes
    On.
    When to change it
    Keep it wherever the team answers chats during the day. Where one person handles all the chats, turn it off and let the reminders reach that person through the bell and the chat bar.
    For example
    The assistant hands over a chat about changing the car on an order; somebody answers within the minute.

    Sound volume

    One level, from 0 to 100, for every notification sound. It scales all kinds alike and applies to everyone signed in, in their own browser. The lowest level makes the sounds silent; it does not switch them off.

    How it comes
    Sixty.
    When to change it
    Set it for the noisier room the portal is used in, and let the office turn its own speakers down.
    For example
    A laptop on the workbench cannot be heard over the compressor until the level goes to the top.

    How shops use it

    Email that looks like the shop, not like a machine

    A remap shop with its own domain and a mailbox at its web host

    Customers were leaving "your file is ready" in spam because it came from an address they did not know. The owner picks Your mail server, lets the setup wizard try the host's details, and sets the sender to the files address on the shop's domain with the shop's name beside it. A test email lands in the inbox.

    Customers recognise the sender, replies reach the shop's normal mailbox, and deliveries stop going unread.

    Three tuners, and each hears only their own work

    A file service with three tuners and an owner who does not tune

    Every upload and every message used to reach everybody by email and bell. The owner leaves new jobs with the staff who can take them and messages with the people on the job, mutes notice emails for the tuner role, and keeps the payment and problem sounds on the workshop screen.

    A tuner is interrupted only for work that is his; the owner hears money and faults and nothing else.

    A workshop where nobody sits at a screen

    A two-person shop that tunes on the dyno most of the day

    New jobs waited until somebody walked past the laptop. The owner makes an app in his own OneSignal account, pastes its app ID and key under Browser push notices and ticks two kinds: new jobs and payments. Both tuners allow notices in the browser on their phones. On the workshop screen, the volume goes to the top and the problem sound stays on.

    A new file buzzes two phones within seconds, the small steps of each job stay quiet, and a failed delivery is heard across the workshop.

    A dealer who uploads forty files before lunch

    A master whose biggest dealer sends files in batches

    Each batch meant forty emails to the tuner, then forty more as the files were delivered. The master lowers the ceiling on emails to one person an hour and narrows push to new jobs and payments. The notices past the ceiling stay on the bell.

    The tuner's inbox stays readable, and no notice is lost: every one is on the bell.

    Where it helps, and its limits

    Where it helps most

    • When "your file is ready" has to arrive from an address your customers know, on your own domain.
    • When the team has grown past two and everybody is being told everything.
    • When tuners are at the car or the dyno, not at a desk, and a new job must reach a phone by push.
    • When the portal sits open on a workshop screen and a sound is how a job gets noticed.
    • When a failed delivery in the evening must be seen before the customer rings in the morning.
    • When the owner wants last month's figures without opening a report.

    What it does not do

    • A notice held back by the hourly ceiling is not emailed later; it stays on the bell in the portal.
    • Sounds need an open portal page. For a closed browser, use push, Telegram or the Messages app of the inbox.
    • Push to browsers needs your own OneSignal account, and sending from your own domain needs your own mailbox; the portal connects to them and does not provide them.
    • The sound volume and the kinds of sound are set for the whole portal, not for each person.

    Which package

    Email
    In every plan, Start included.
    Who is told what
    In every plan, Start included.
    Sounds
    In every plan, Start included.

    Prices in euros, a month, before tax, billed on the 1st. Every price ›

    Questions shops ask

    Can the portal send email from my own domain?
    Yes. Choose Your mail server, enter the details your email provider gives you and set the sender address on that domain. The setup wizard fills the details for the well-known providers and tries them before they are kept.
    If I switch notice emails off, can customers still sign in and reset passwords?
    Yes. Sign-in codes, password resets, receipts, invoices and security notices are never stopped by that switch, by the hourly ceiling or by a muted role.
    How do I stop the emails to my tuners without stopping them for customers?
    Leave Notice emails on and tick the tuner role under Roles that get no notice emails. The tuners keep the bell, Telegram and push.
    Gmail says the password is wrong, but it is right. Why?
    Google wants an app password, made in your Google account under Security, not the one you sign in with. Microsoft may need an administrator to allow the mailbox to send this way.
    Are emails held back by the hourly ceiling sent later?
    No. A notice past the ceiling is kept on the bell in the portal only, and the next hour starts a fresh count. The ceiling is counted for each email address separately.
    I ticked no kinds under Notices sent by push. Does that mean no push?
    The opposite: nothing ticked means every kind is pushed. To stop push entirely, switch off Browser push notices.
    What is the difference between push and the Messages app?
    Push through OneSignal carries the portal's notices to browsers and phones, and needs your own OneSignal account. The Messages app on the team's phones rings about customer conversations by itself; it is set up with the inbox.
    If only the people on a job are told about a message, can nobody else step in?
    Anybody who may work the job can. The queue shows every open job; the setting changes who is interrupted, not who can see. While a job is unclaimed, the staff who could take it are told as well.
    Can each member of staff have their own sound volume?
    The level is the portal's. Each person can turn their own computer or browser down, and each kind of sound has its own switch for the whole portal.
    Which package do I need?
    Email, the notification rules, push and the sounds come with every package.

    Guides that go deeper

    Every function of the portal, each on its own page. All functions

    Start my portalEvery price

    Name your portal. It is ready in under a minute.

    • Your name and logo
    • Files from any tool
    • Updates done for you
    • Moving in free on paid plans

    You can change your portal's address from your account at any time, or add another to the same portal, free. More are coming: tunerengine.co.uk, tunerengine.uk and tunerengine.info, then new short ones made for portals.