Clearer recipient and link limits for customer emails
When you change the business contact email in settings, the new address awaits confirmation. You can send a confirmation link or cancel the change. The current address remains in use so invoicing and emails can continue. Your own verified login address can be used immediately.
When you change the business contact email in settings, the new address awaits confirmation. You can send a confirmation link or cancel the change. The current address remains in use so invoicing and emails can continue. Your own verified login address can be used immediately.
A manually sent message can have up to 10 distinct recipient addresses. Duplicates count once. When you choose email during document creation, the list is checked before creation. It is also checked before delivery reserves customer contact.
When you edit a customer email template, you can format the text and include contact email addresses, and use approved website links, for example to alunta.com, app.alunta.com or your own company website after manual approval. Other web links are rejected, including typed web addresses. The email’s built-in payment, signup and portal buttons remain available. Ordinary PDF filenames and abbreviations are still supported. Errors involving links, hidden email recipients or too many blank lines appear next to the field before saving and previewing. Existing saved links are not automatically changed.
New and changed customer names cannot contain actual links. Ordinary business names such as Clerk.io remain valid, and an existing name can be retained when you edit other details. If an accounting refresh refuses an imported name, you receive an explanation and can deselect the name change to apply the remaining details.


The people and AI helpers behind the updates
Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.
The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.
