Help by DeltaBreen
Sign inStart free

One flat price. Never per agent.

A plan covers your whole workspace and the team it includes. If you use more tickets than your plan has, we email you. We never send a surprise bill.

A new request from one of your customers. Replies on it are free, and spam doesn't count.
Everyone who can use the workspace, including you. The plan's price covers all of them.
A website or app with its own form, integrations and tickets.
Verified domains
Form and "my tickets" page in your site
WordPress plugin
Bring your tickets, replies and private notes over from the helpdesk you use now. It doesn't count toward your plan's tickets.
Reply emails a day
Your customers answer our emails from their own mail program, and what they write joins the ticket.
Forward your own support address to Help, and each email becomes a ticket.
The buttons in our emails to your customers open their tickets on your own help page, so they stay with you.
Emails to your customers come from your own address, through your own mail server. They don't count toward your reply emails a day.
What your form asks before the message, like an order number. Severity and category are ready-made on every plan.
Name the states your tickets go through, such as "Waiting on supplier", each of one kind. On hold, for a ticket waiting on someone else, is on every plan.
Fields only your team sees on a ticket, such as a bug number or a refund amount. Never shown to your customer.
Answers you give often, put into a reply in one click with the customer's name and the ticket's number filled in.
Your customers and your team can send screenshots and files with a message. When your storage is full, new files are refused and nothing is billed. Files go when their ticket is deleted.
Browser notifications
When a ticket becomes urgent, the people on call get a text, then a call if nobody has opened it. It goes through your own Twilio or Vonage account.
A message in your team's channel in Slack, Teams, Discord or Telegram when a ticket arrives. It names the ticket and never what your customer wrote.
How many tickets came in, how many you answered and closed, and how long the first reply took, by day, by site and by teammate.
Log the time spent on each ticket, typed in or with a timer, and see it totalled by teammate and by site in Reports.
Say how soon you reply, by priority and in your working hours. Each waiting ticket shows its time, and late ones come first. On Business, customers on your bigger plans can have shorter times.
Answers your customers read inside your own site. Your form suggests the ones that match while a customer writes, so some questions never become tickets.
Ask customers “How did we do?” once a ticket is closed: one to five stars and a line of their own. Reports count the stars by site and by teammate.
See your tickets as lanes, from New to Closed, and move a ticket by dragging its card. You can keep your own order in each lane.
Change many tickets in one go, see who else has a ticket open so two people don't answer it, mention a teammate in a private note, and merge two tickets from the same customer.
A ticket can be a team's as well as a person's, each team has its own queue, and new tickets go to a team by their site or a tag.
Group the people who write in by the business they work for, by their email's domain or by what your site signs.
New tickets handed out to your team in turn, a tag added from what the form was answered with, quiet tickets closed, and an away message outside your working hours.
Form design
DeltaBreen badge
A URL on your server that we ask about a customer, so your team sees who they are next to the ticket. We show the answer and don't store it.
See a customer's Stripe subscriptions and charges, or their Shopify orders, next to their ticket. We show it and keep none of it.
Make an issue from a ticket in one click. It carries your words and a link to the ticket, never what your customer wrote.
Buttons next to the ticket that do something in your system, like cancel a subscription or refund an order. The agent types a word first, so nothing runs by accident.
Connect Claude, ChatGPT, Cursor or any assistant that speaks MCP, and let it answer tickets and set things up. You choose what it can do. We don't run any AI ourselves.
Read, reply to, change and open tickets from your own code, with a key you make.
We tell your own code, Zapier, Make or n8n when a ticket arrives, gets a reply or changes.
Closed tickets kept for
Audit log
Anyone can sign in with an authenticator app. On Business the owner can require it of everyone in the workspace.
Your team signs in through your own provider, such as Microsoft Entra ID, Google Workspace or Okta, and you can require it for everyone at your email domain.
Give someone some of an admin's powers and not the rest, let a role see only its own tickets, or keep it to private notes.
If you go over
Signed DPA

Free

For a small site that wants a proper support form and a ticket board.

€0/month

No card needed

Start free
A new request from one of your customers. Replies on it are free, and spam doesn't count.
Tickets: 100
Everyone who can use the workspace, including you. The plan's price covers all of them.
People: 2
A website or app with its own form, integrations and tickets.
Sites: 1
Verified domains
Verified domains: 1
Form and "my tickets" page in your site
Form and "my tickets" page in your site:
WordPress plugin
WordPress plugin:
Bring your tickets, replies and private notes over from the helpdesk you use now. It doesn't count toward your plan's tickets.
Import your old tickets:
Reply emails
Reply emails: 30
Your customers answer our emails from their own mail program, and what they write joins the ticket.
Replies by email:
Forward your own support address to Help, and each email becomes a ticket.
Your support mail as tickets: —
The buttons in our emails to your customers open their tickets on your own help page, so they stay with you.
Replies open on your site:
Emails to your customers come from your own address, through your own mail server. They don't count toward your reply emails a day.
Your own mail server: —
What your form asks before the message, like an order number. Severity and category are ready-made on every plan.
Form fields: Severity and category
Name the states your tickets go through, such as "Waiting on supplier", each of one kind. On hold, for a ticket waiting on someone else, is on every plan.
Statuses of your own: —
Fields only your team sees on a ticket, such as a bug number or a refund amount. Never shown to your customer.
Team fields: —
Answers you give often, put into a reply in one click with the customer's name and the ticket's number filled in.
Saved replies: 5
Your customers and your team can send screenshots and files with a message. When your storage is full, new files are refused and nothing is billed. Files go when their ticket is deleted.
Attachments: —
Browser notifications
Browser notifications:
When a ticket becomes urgent, the people on call get a text, then a call if nobody has opened it. It goes through your own Twilio or Vonage account.
Texts and calls when urgent: —
A message in your team's channel in Slack, Teams, Discord or Telegram when a ticket arrives. It names the ticket and never what your customer wrote.
Team chat alerts: —
How many tickets came in, how many you answered and closed, and how long the first reply took, by day, by site and by teammate.
Reports: —
Log the time spent on each ticket, typed in or with a timer, and see it totalled by teammate and by site in Reports.
Time tracking: —
Say how soon you reply, by priority and in your working hours. Each waiting ticket shows its time, and late ones come first. On Business, customers on your bigger plans can have shorter times.
Reply times: —
Answers your customers read inside your own site. Your form suggests the ones that match while a customer writes, so some questions never become tickets.
Help articles: —
Ask customers “How did we do?” once a ticket is closed: one to five stars and a line of their own. Reports count the stars by site and by teammate.
Ratings: —
See your tickets as lanes, from New to Closed, and move a ticket by dragging its card. You can keep your own order in each lane.
Board:
Change many tickets in one go, see who else has a ticket open so two people don't answer it, mention a teammate in a private note, and merge two tickets from the same customer.
Team tools: —
A ticket can be a team's as well as a person's, each team has its own queue, and new tickets go to a team by their site or a tag.
Teams: —
Group the people who write in by the business they work for, by their email's domain or by what your site signs.
Companies: —
New tickets handed out to your team in turn, a tag added from what the form was answered with, quiet tickets closed, and an away message outside your working hours.
Rules: —
Form design
Form design: Your words and colour
DeltaBreen badge
DeltaBreen badge: Shown
A URL on your server that we ask about a customer, so your team sees who they are next to the ticket. We show the answer and don't store it.
Integrations: —
See a customer's Stripe subscriptions and charges, or their Shopify orders, next to their ticket. We show it and keep none of it.
Stripe and Shopify: —
Make an issue from a ticket in one click. It carries your words and a link to the ticket, never what your customer wrote.
Issues in GitHub, Linear or Jira: —
Buttons next to the ticket that do something in your system, like cancel a subscription or refund an order. The agent types a word first, so nothing runs by accident.
Buttons: —
Connect Claude, ChatGPT, Cursor or any assistant that speaks MCP, and let it answer tickets and set things up. You choose what it can do. We don't run any AI ourselves.
Your own AI assistant: —
Read, reply to, change and open tickets from your own code, with a key you make.
API: —
We tell your own code, Zapier, Make or n8n when a ticket arrives, gets a reply or changes.
Webhooks: —
Closed tickets kept for
Closed tickets kept for: 90 days
Audit log
Audit log: —
Anyone can sign in with an authenticator app. On Business the owner can require it of everyone in the workspace.
Two-step sign-in:
Your team signs in through your own provider, such as Microsoft Entra ID, Google Workspace or Okta, and you can require it for everyone at your email domain.
Single sign-on: —
Give someone some of an admin's powers and not the rest, let a role see only its own tickets, or keep it to private notes.
Roles of your own: —
If you go over
If you go over: Form pauses
Signed DPA
Signed DPA: —

Lite

For a shop or WordPress site that wants to see the customer next to the ticket.

€10/month

Billed monthly, cancel any time

Choose Lite
A new request from one of your customers. Replies on it are free, and spam doesn't count.
Tickets: 1,000
Everyone who can use the workspace, including you. The plan's price covers all of them.
People: 3
A website or app with its own form, integrations and tickets.
Sites: 1
Verified domains
Verified domains: 3
Form and "my tickets" page in your site
Form and "my tickets" page in your site:
WordPress plugin
WordPress plugin:
Bring your tickets, replies and private notes over from the helpdesk you use now. It doesn't count toward your plan's tickets.
Import your old tickets:
Reply emails
Reply emails: 200
Your customers answer our emails from their own mail program, and what they write joins the ticket.
Replies by email:
Forward your own support address to Help, and each email becomes a ticket.
Your support mail as tickets:
The buttons in our emails to your customers open their tickets on your own help page, so they stay with you.
Replies open on your site:
Emails to your customers come from your own address, through your own mail server. They don't count toward your reply emails a day.
Your own mail server: —
What your form asks before the message, like an order number. Severity and category are ready-made on every plan.
Form fields: 3 of your own
Name the states your tickets go through, such as "Waiting on supplier", each of one kind. On hold, for a ticket waiting on someone else, is on every plan.
Statuses of your own: 5
Fields only your team sees on a ticket, such as a bug number or a refund amount. Never shown to your customer.
Team fields: 3
Answers you give often, put into a reply in one click with the customer's name and the ticket's number filled in.
Saved replies: Unlimited
Your customers and your team can send screenshots and files with a message. When your storage is full, new files are refused and nothing is billed. Files go when their ticket is deleted.
Attachments: 2 GB of files
Browser notifications
Browser notifications:
When a ticket becomes urgent, the people on call get a text, then a call if nobody has opened it. It goes through your own Twilio or Vonage account.
Texts and calls when urgent: —
A message in your team's channel in Slack, Teams, Discord or Telegram when a ticket arrives. It names the ticket and never what your customer wrote.
Team chat alerts: —
How many tickets came in, how many you answered and closed, and how long the first reply took, by day, by site and by teammate.
Reports: —
Log the time spent on each ticket, typed in or with a timer, and see it totalled by teammate and by site in Reports.
Time tracking: —
Say how soon you reply, by priority and in your working hours. Each waiting ticket shows its time, and late ones come first. On Business, customers on your bigger plans can have shorter times.
Reply times: —
Answers your customers read inside your own site. Your form suggests the ones that match while a customer writes, so some questions never become tickets.
Help articles: —
Ask customers “How did we do?” once a ticket is closed: one to five stars and a line of their own. Reports count the stars by site and by teammate.
Ratings: —
See your tickets as lanes, from New to Closed, and move a ticket by dragging its card. You can keep your own order in each lane.
Board:
Change many tickets in one go, see who else has a ticket open so two people don't answer it, mention a teammate in a private note, and merge two tickets from the same customer.
Team tools:
A ticket can be a team's as well as a person's, each team has its own queue, and new tickets go to a team by their site or a tag.
Teams: —
Group the people who write in by the business they work for, by their email's domain or by what your site signs.
Companies: —
New tickets handed out to your team in turn, a tag added from what the form was answered with, quiet tickets closed, and an away message outside your working hours.
Rules: —
Form design
Form design: Your own HTML & CSS
DeltaBreen badge
DeltaBreen badge: None
A URL on your server that we ask about a customer, so your team sees who they are next to the ticket. We show the answer and don't store it.
Integrations: 1
See a customer's Stripe subscriptions and charges, or their Shopify orders, next to their ticket. We show it and keep none of it.
Stripe and Shopify: —
Make an issue from a ticket in one click. It carries your words and a link to the ticket, never what your customer wrote.
Issues in GitHub, Linear or Jira: —
Buttons next to the ticket that do something in your system, like cancel a subscription or refund an order. The agent types a word first, so nothing runs by accident.
Buttons: —
Connect Claude, ChatGPT, Cursor or any assistant that speaks MCP, and let it answer tickets and set things up. You choose what it can do. We don't run any AI ourselves.
Your own AI assistant: —
Read, reply to, change and open tickets from your own code, with a key you make.
API: —
We tell your own code, Zapier, Make or n8n when a ticket arrives, gets a reply or changes.
Webhooks: —
Closed tickets kept for
Closed tickets kept for: 1 year
Audit log
Audit log: —
Anyone can sign in with an authenticator app. On Business the owner can require it of everyone in the workspace.
Two-step sign-in:
Your team signs in through your own provider, such as Microsoft Entra ID, Google Workspace or Okta, and you can require it for everyone at your email domain.
Single sign-on: —
Give someone some of an admin's powers and not the rest, let a role see only its own tickets, or keep it to private notes.
Roles of your own: —
If you go over
If you go over: Keeps working
Signed DPA
Signed DPA: —

Pro

For a support team that wants to fix things without leaving the ticket.

€49/month

Billed monthly, cancel any time

Choose Pro
A new request from one of your customers. Replies on it are free, and spam doesn't count.
Tickets: 3,000
Everyone who can use the workspace, including you. The plan's price covers all of them.
People: 10
A website or app with its own form, integrations and tickets.
Sites: 3
Verified domains
Verified domains: 10
Form and "my tickets" page in your site
Form and "my tickets" page in your site:
WordPress plugin
WordPress plugin:
Bring your tickets, replies and private notes over from the helpdesk you use now. It doesn't count toward your plan's tickets.
Import your old tickets:
Reply emails
Reply emails: 1,000
Your customers answer our emails from their own mail program, and what they write joins the ticket.
Replies by email:
Forward your own support address to Help, and each email becomes a ticket.
Your support mail as tickets:
The buttons in our emails to your customers open their tickets on your own help page, so they stay with you.
Replies open on your site:
Emails to your customers come from your own address, through your own mail server. They don't count toward your reply emails a day.
Your own mail server: —
What your form asks before the message, like an order number. Severity and category are ready-made on every plan.
Form fields: 10 of your own
Name the states your tickets go through, such as "Waiting on supplier", each of one kind. On hold, for a ticket waiting on someone else, is on every plan.
Statuses of your own: 20
Fields only your team sees on a ticket, such as a bug number or a refund amount. Never shown to your customer.
Team fields: 10
Answers you give often, put into a reply in one click with the customer's name and the ticket's number filled in.
Saved replies: Unlimited
Your customers and your team can send screenshots and files with a message. When your storage is full, new files are refused and nothing is billed. Files go when their ticket is deleted.
Attachments: 20 GB of files
Browser notifications
Browser notifications:
When a ticket becomes urgent, the people on call get a text, then a call if nobody has opened it. It goes through your own Twilio or Vonage account.
Texts and calls when urgent: —
A message in your team's channel in Slack, Teams, Discord or Telegram when a ticket arrives. It names the ticket and never what your customer wrote.
Team chat alerts:
How many tickets came in, how many you answered and closed, and how long the first reply took, by day, by site and by teammate.
Reports:
Log the time spent on each ticket, typed in or with a timer, and see it totalled by teammate and by site in Reports.
Time tracking:
Say how soon you reply, by priority and in your working hours. Each waiting ticket shows its time, and late ones come first. On Business, customers on your bigger plans can have shorter times.
Reply times:
Answers your customers read inside your own site. Your form suggests the ones that match while a customer writes, so some questions never become tickets.
Help articles: 200
Ask customers “How did we do?” once a ticket is closed: one to five stars and a line of their own. Reports count the stars by site and by teammate.
Ratings:
See your tickets as lanes, from New to Closed, and move a ticket by dragging its card. You can keep your own order in each lane.
Board:
Change many tickets in one go, see who else has a ticket open so two people don't answer it, mention a teammate in a private note, and merge two tickets from the same customer.
Team tools:
A ticket can be a team's as well as a person's, each team has its own queue, and new tickets go to a team by their site or a tag.
Teams:
Group the people who write in by the business they work for, by their email's domain or by what your site signs.
Companies:
New tickets handed out to your team in turn, a tag added from what the form was answered with, quiet tickets closed, and an away message outside your working hours.
Rules:
Form design
Form design: Your own HTML & CSS
DeltaBreen badge
DeltaBreen badge: None
A URL on your server that we ask about a customer, so your team sees who they are next to the ticket. We show the answer and don't store it.
Integrations: 5
See a customer's Stripe subscriptions and charges, or their Shopify orders, next to their ticket. We show it and keep none of it.
Stripe and Shopify:
Make an issue from a ticket in one click. It carries your words and a link to the ticket, never what your customer wrote.
Issues in GitHub, Linear or Jira: 3
Buttons next to the ticket that do something in your system, like cancel a subscription or refund an order. The agent types a word first, so nothing runs by accident.
Buttons:
Connect Claude, ChatGPT, Cursor or any assistant that speaks MCP, and let it answer tickets and set things up. You choose what it can do. We don't run any AI ourselves.
Your own AI assistant:
Read, reply to, change and open tickets from your own code, with a key you make.
API:
We tell your own code, Zapier, Make or n8n when a ticket arrives, gets a reply or changes.
Webhooks: 3
Closed tickets kept for
Closed tickets kept for: 1 year
Audit log
Audit log:
Anyone can sign in with an authenticator app. On Business the owner can require it of everyone in the workspace.
Two-step sign-in:
Your team signs in through your own provider, such as Microsoft Entra ID, Google Workspace or Okta, and you can require it for everyone at your email domain.
Single sign-on: —
Give someone some of an admin's powers and not the rest, let a role see only its own tickets, or keep it to private notes.
Roles of your own: —
If you go over
If you go over: Keeps working
Signed DPA
Signed DPA: —

Business

For several sites and a bigger team.

€129/month

Billed monthly, cancel any time

Choose Business
A new request from one of your customers. Replies on it are free, and spam doesn't count.
Tickets: 10,000
Everyone who can use the workspace, including you. The plan's price covers all of them.
People: 15
A website or app with its own form, integrations and tickets.
Sites: 10
Verified domains
Verified domains: Unlimited
Form and "my tickets" page in your site
Form and "my tickets" page in your site:
WordPress plugin
WordPress plugin:
Bring your tickets, replies and private notes over from the helpdesk you use now. It doesn't count toward your plan's tickets.
Import your old tickets:
Reply emails
Reply emails: 3,000
Your customers answer our emails from their own mail program, and what they write joins the ticket.
Replies by email:
Forward your own support address to Help, and each email becomes a ticket.
Your support mail as tickets:
The buttons in our emails to your customers open their tickets on your own help page, so they stay with you.
Replies open on your site:
Emails to your customers come from your own address, through your own mail server. They don't count toward your reply emails a day.
Your own mail server:
What your form asks before the message, like an order number. Severity and category are ready-made on every plan.
Form fields: Unlimited
Name the states your tickets go through, such as "Waiting on supplier", each of one kind. On hold, for a ticket waiting on someone else, is on every plan.
Statuses of your own: Unlimited
Fields only your team sees on a ticket, such as a bug number or a refund amount. Never shown to your customer.
Team fields: Unlimited
Answers you give often, put into a reply in one click with the customer's name and the ticket's number filled in.
Saved replies: Unlimited
Your customers and your team can send screenshots and files with a message. When your storage is full, new files are refused and nothing is billed. Files go when their ticket is deleted.
Attachments: 100 GB of files
Browser notifications
Browser notifications:
When a ticket becomes urgent, the people on call get a text, then a call if nobody has opened it. It goes through your own Twilio or Vonage account.
Texts and calls when urgent:
A message in your team's channel in Slack, Teams, Discord or Telegram when a ticket arrives. It names the ticket and never what your customer wrote.
Team chat alerts:
How many tickets came in, how many you answered and closed, and how long the first reply took, by day, by site and by teammate.
Reports: With CSV download
Log the time spent on each ticket, typed in or with a timer, and see it totalled by teammate and by site in Reports.
Time tracking:
Say how soon you reply, by priority and in your working hours. Each waiting ticket shows its time, and late ones come first. On Business, customers on your bigger plans can have shorter times.
Reply times: By customer plan
Answers your customers read inside your own site. Your form suggests the ones that match while a customer writes, so some questions never become tickets.
Help articles: Unlimited
Ask customers “How did we do?” once a ticket is closed: one to five stars and a line of their own. Reports count the stars by site and by teammate.
Ratings:
See your tickets as lanes, from New to Closed, and move a ticket by dragging its card. You can keep your own order in each lane.
Board:
Change many tickets in one go, see who else has a ticket open so two people don't answer it, mention a teammate in a private note, and merge two tickets from the same customer.
Team tools:
A ticket can be a team's as well as a person's, each team has its own queue, and new tickets go to a team by their site or a tag.
Teams:
Group the people who write in by the business they work for, by their email's domain or by what your site signs.
Companies:
New tickets handed out to your team in turn, a tag added from what the form was answered with, quiet tickets closed, and an away message outside your working hours.
Rules:
Form design
Form design: Your own HTML & CSS
DeltaBreen badge
DeltaBreen badge: None
A URL on your server that we ask about a customer, so your team sees who they are next to the ticket. We show the answer and don't store it.
Integrations: Unlimited
See a customer's Stripe subscriptions and charges, or their Shopify orders, next to their ticket. We show it and keep none of it.
Stripe and Shopify:
Make an issue from a ticket in one click. It carries your words and a link to the ticket, never what your customer wrote.
Issues in GitHub, Linear or Jira: 10
Buttons next to the ticket that do something in your system, like cancel a subscription or refund an order. The agent types a word first, so nothing runs by accident.
Buttons:
Connect Claude, ChatGPT, Cursor or any assistant that speaks MCP, and let it answer tickets and set things up. You choose what it can do. We don't run any AI ourselves.
Your own AI assistant:
Read, reply to, change and open tickets from your own code, with a key you make.
API:
We tell your own code, Zapier, Make or n8n when a ticket arrives, gets a reply or changes.
Webhooks: 10
Closed tickets kept for
Closed tickets kept for: You choose
Audit log
Audit log:
Anyone can sign in with an authenticator app. On Business the owner can require it of everyone in the workspace.
Two-step sign-in: Required for everyone
Your team signs in through your own provider, such as Microsoft Entra ID, Google Workspace or Okta, and you can require it for everyone at your email domain.
Single sign-on:
Give someone some of an admin's powers and not the rest, let a role see only its own tickets, or keep it to private notes.
Roles of your own:
If you go over
If you go over: Keeps working
Signed DPA
Signed DPA: On request

Enterprise

More than 15 people, or more than 10,000 tickets a month? From €399 a month, billed yearly. You get room for your whole team, a ticket allowance sized to it, a named contact and a signed DPA. If you grow past what we agreed, we talk first. Nothing is paused and nothing extra is billed.

Talk to us

Included in every plan

  • Inside your own site. A support form and a "my tickets" page your customers use without leaving you.
  • No price per agent. Every plan includes a team, and its price covers all of them.
  • Every ticket in one place. Replies, private notes, who's handling what and where each one stands.
  • No surprise bills. Paid plans keep working if you go over. Free pauses. You're never charged extra.
  • Servers in the EU. A GDPR data processing agreement for every account.

Questions

Do you charge per agent?

No. The price is for the whole workspace, and each plan includes a number of people. You pay the same whether one of them answers tickets or all of them. For a bigger team than Business includes, talk to us about Enterprise.

What counts as a ticket?

A new request from one of your customers. Every reply on it, from them or from you, is part of the same ticket. Spam and test tickets don't count.

What happens if I go over my plan?

You're never charged extra. On a paid plan the form keeps working, and we get in touch about the right plan. On Free, the form stops taking messages from guests until the month ends. We email you at 80% so it's never a surprise.

What does an integration store about my customers?

Nothing. When an agent opens a ticket we ask your URL about that customer, show the answer in the side panel, and keep none of it. It's not in our database and not in our logs. We only keep which fields you chose to show.

Does Help use AI on my tickets?

No. Help doesn't run any AI, on any plan, and nothing you or your customers write is sent to a model by us. On Pro and higher you can connect your own assistant. You choose what it can do, and it only sees the customer details you mark for it.

How do customers get replies?

Logged-in customers see them on the "my tickets" page inside your own site. Anyone who gave their email also gets the reply by email, with a link to answer, once they've confirmed the address.

How do billing, VAT and cancelling work?

Paddle handles payment for us. It runs the checkout, sends invoices and deals with VAT, and prices include VAT. You can change plan or cancel any time under Plan & billing. An upgrade starts straight away, and moving to a smaller plan deletes nothing. A yearly plan costs ten months.

Who runs Help by DeltaBreen?

DeltaBreen Limited, a company registered in Ireland (number 826627), in Gorey, Co. Wexford, Ireland. Our servers are in the EU, and the people who build the service answer your support questions.

Prices include VAT. Paddle handles payment for paid plans. Questions about a contract? Email [email protected].