How to Build a Customer Exception Register for Discounts, Refunds and Special Terms
A customer complains about a delayed service call. A manager approves a $150 credit and promises priority scheduling on the next visit.
Three months later, the customer requests another discount. The employee handling the call sees the previous credit but cannot determine why it was granted, whether the priority promise still applies or who authorized it.
The customer says, “Your manager already approved this.”
Nobody can prove otherwise.
One-time accommodations are necessary in most businesses. The problem begins when discounts, refunds and special terms are scattered across email, invoices, text messages and employee memory.
Exceptions Quietly Become Unofficial Policy
Customer exceptions may include:
- Refunds and service credits
- Pricing overrides
- Free return visits
- Extended payment terms
- Waived fees
- Priority scheduling
- Additional work outside the contract
- Special communication requirements
- Replacement products or upgraded services
- Commitments made after a complaint
Without a controlled record, employees cannot distinguish an approved exception from a permanent entitlement.
One employee may continue honoring an expired promise. Another may refuse an agreement the company intended to maintain. Managers repeatedly investigate old conversations before making decisions.
Pricing systems can store customer-specific prices, discounts, effective dates and eligibility conditions. Microsoft Business Central supports special price agreements for individual customers or customer groups. Dynamics 365 can also require workflow approval when a price override exceeds an established threshold. The technology works only when the organization has defined the underlying authority and conditions.
Record the Reason, Not Just the Amount
A useful exception register should explain the decision rather than merely recording that a discount occurred.
Each entry should include:
- Customer and related job, invoice or contract
- Type and value of the exception
- Reason it was granted
- Employee who requested it
- Manager or role that approved it
- Conditions attached to the decision
- Effective and expiration dates
- Whether it applies once or to future work
- Supporting email, complaint or service record
- Follow-up action and final outcome
Suppose a customer receives a free return visit because the original technician missed a documented step. That is different from a goodwill visit approved because severe weather delayed the appointment.
The first event may require corrective training. The second may require no operational change. Recording only “no charge” destroys the context.
Separate Standard Policies From Customer Exceptions
The company should maintain an approved policy defining what employees may offer without additional approval.
For example:
- Customer-service employees may approve credits up to $50.
- Department managers may approve refunds up to $500.
- Contract changes require an executive or account owner.
- Safety, legal and regulatory complaints must be escalated.
- Recurring discounts require a documented customer agreement.
- Exceptions expire unless explicitly renewed.
The exception register records decisions outside or alongside those standard rules. It should never silently rewrite the company’s pricing or refund policy.
This distinction helps retain institutional knowledge while preventing yesterday’s emergency decision from becoming tomorrow’s standard operating procedure.
Customer-specific instructions are especially important in firms where employees handle several accounts with different expectations. Bookkeeping firms may have unique approval procedures, deadlines and service arrangements for each client. Commercial cleaning companies may need documented complaint-escalation and service-recovery rules for individual facilities.
Review Patterns Across Exceptions
An exception register is not only a historical record. It can expose operational problems.
Review it monthly or quarterly for patterns such as:
- One service generating repeated credits
- One customer receiving recurring undocumented discounts
- One branch issuing more refunds than others
- Promises repeatedly made outside contract terms
- Complaints caused by the same process failure
- Managers applying different remedies to similar cases
Repeated exceptions may indicate that the standard policy, pricing model, training or service process needs correction.
How Maisy Makes Approved Exceptions Searchable
Maisy can make approved exception records, customer instructions and authorization policies searchable through Microsoft 365.
An authorized employee could ask:
“What credit was approved for this customer and why?”
“Does the priority-scheduling promise still apply?”
“Who can approve a refund above $500?”
“Has this customer previously received a waiver for the same issue?”
Pixeldust organizes the records in SharePoint, applies ownership and review dates, and separates general policies from customer-specific information. Microsoft 365 groups determine which employees can view financial terms, complaints or contract details. During testing, employees use realistic questions to verify that answers and permissions work correctly.
This allows the company to retain institutional knowledge without letting every exception live forever in somebody’s inbox. A favor should remain a documented decision—not become company folklore.