Solido

Common Mistakes to Avoid

Common Mistakes to Avoid

Solido rules work best when they are short, directive, and focused on tone and style. Each reminder stage lets you add multiple rules, and Solido combines them with the invoice details it already knows: the customer name, invoice number, amount, and due date. Your rules just need to tell Solido how to say it, not what to say.

Here are the six most common mistakes we see, and how to fix each one.

1. Being Too Vague

A rule that gives Solido no direction forces it to guess at tone, length, and emphasis. The result is a generic email that could have come from any company.

No guidance on tone, length, or emphasis Avoid

Send a reminder.

Instead, give Solido a clear directive. Even a single sentence is enough if it describes how the email should feel.

Short but specific: sets tone and intent Good

Keep it brief and friendly. Just a courtesy heads-up that the invoice is coming due.

2. Hardcoding Variable Data

Solido automatically pulls the customer name, invoice number, amount, and due date from Xero and inserts them into every email. When you put these details in your rules, the same hardcoded data gets applied to every customer, which means every email except one will contain the wrong information.

Hardcodes customer name, invoice number, and amount Avoid

Remind ABC Ltd that invoice #1042 for $5,250 is due.

Focus your rule on how the email should read. Let Solido handle the data.

Focuses on tone: Solido fills in the details Good

Be polite but direct. Mention that this is a reminder and the invoice is now overdue.

Never put invoice details in your rules

Invoice numbers, amounts, due dates, and customer names are all inserted automatically by Solido. Including them in your rule will cause incorrect information to appear in emails sent to other customers.

3. Giving Conflicting Instructions

Because you can add multiple rules per reminder stage, it is easy to accidentally send mixed signals. If one rule says “be friendly and casual” and another says “be very firm about consequences,” Solido has to choose. The result is an email that feels inconsistent.

Combined with another rule that says 'Be very firm about consequences' Avoid

Be friendly and casual.

Pick one tone direction per stage. All the rules within a single stage should point the same way.

Clear, consistent direction: all rules in this stage should match Good

Keep the tone warm and professional.

4. Forgetting Reminder Stage Context

Each reminder stage represents a different moment in the collections timeline. A pre-due nudge is not the same as a 30-day overdue follow-up. Using identical rules across all stages produces a flat sequence that never escalates and loses its effectiveness.

Same rule copy-pasted across all stages Avoid

Please remind the customer to pay their invoice. Be professional.

Write different rules for each stage so the tone and urgency increase naturally over time.

Stage 3 example Acknowledges the stage and escalates appropriately Good

This is a second follow-up. Be more direct than the first reminder and ask the customer to confirm when payment will be made.

5. Threatening Language in Early Stages

Jumping to threats in a first or second reminder damages customer relationships. Most overdue invoices are the result of oversight, not avoidance. Aggressive language early on makes customers less likely to pay and more likely to dispute.

Threatening language on a first reminder Avoid

Tell them we'll take legal action.

In early stages, assume good intent. Keep the door open for the customer to respond.

Assumes good intent, appropriate for early stages Good

Assume they may have missed it. Offer to help if there are any questions.

The good-intent rule

For stages 1 through 3 of your reminder sequence, always write your rules assuming the customer intends to pay and simply needs a nudge. Reserve mentions of consequences for stage 4 and beyond.

6. Writing Paragraph-Length Rules

Rules are directives, not drafts. When you write a paragraph that describes every detail of the email you want, you are doing Solido's job for it. Long rules are harder to maintain, more likely to contain contradictions, and do not produce better results than concise ones.

Over-explained: tries to script the email in the rule Avoid

Write a friendly, short email reminding the customer that their invoice is approaching its due date. Thank them for their business and mention the upcoming due date casually. Keep it warm and brief.

Say the same thing in fewer words. Short, directive rules give Solido clear guardrails without micromanaging the output.

Same intent, a fraction of the words Good

Keep it brief and friendly. Thank them for their business.

Summary

Avoiding these six mistakes will immediately improve the quality of the emails Solido generates for you:

  • Be specific: Even a short rule should set a clear tone and intent.
  • Do not hardcode data: Solido pulls invoice details from Xero automatically.
  • Stay consistent: All rules within a stage should point in the same tone direction.
  • Write stage-appropriate rules: Escalate tone and urgency across stages.
  • Save firm language for later: Assume good intent in early stages.
  • Keep rules concise: Short directives outperform paragraph-length instructions.

Review your existing rules against this checklist. Even small adjustments can lead to noticeably better reminder emails.

Give it a try

Setup takes about 10 minutes. Your first reminders can go out today.