> ## Documentation Index
> Fetch the complete documentation index at: https://help.avoca.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Best practices for follow-up to Avoca calls

## Best Practices for Follow-Up to Avoca-Handled Calls

## 1. Purpose & Philosophy

Effective follow-up is critical to maximizing containment, customer satisfaction, and revenue from Avoca-handled calls. The goal of follow-up is to **complete resolution without re-routing customers back to the branch**, while preserving context and continuity from the original interaction.

Follow-up should feel:

* Intentional
* Timely
* Context-aware
* Low-effort for the customer

## 2. When Follow-Up Is Required

Follow-up should be initiated when the original call cannot be fully resolved in real time.

### Common Follow-Up Triggers

* Customer unable to book immediately
* Billing or invoice inquiries requiring review
* ETA or scheduling confirmation requests
* Warranty or membership verification
* Parts availability or job status questions
* Escalations requiring internal review
* Missed connections to a branch or department

## 3. Follow-Up Ownership & Accountability

Every follow-up action must have **clear ownership**.

### Best Practices

* Assign follow-up to a specific team, queue, or role
* Avoid generic inboxes without SLAs
* Maintain visibility within the primary operating system (e.g., service platform or CRM)

**Principle:** If no one owns the follow-up, the customer will call back.

## 4. Structured Follow-Up via Action Items

Action items should be the default follow-up mechanism.

### Best Practices

* Automatically generate structured tasks from call outcomes
* Include:
  * Call summary
  * Customer intent
  * Required next action
  * Suggested resolution path
* Resolve within the same system where operational work occurs

**Avoid:** Email-only follow-ups that fragment ownership and tracking.

## 5. Outbound Callbacks

Callbacks should feel like a continuation of the original conversation.

### Best Practices

* Reference the original call context immediately
* Confirm whether the issue is still relevant before proceeding
* Limit callback attempts and provide alternative resolution options
* Log outcomes consistently to avoid duplicate outreach

## 6. SMS as a Primary Follow-Up Channel

SMS enables fast, low-friction resolution and should be used whenever appropriate.

### Recommended Use Cases

* Booking links for unbooked calls
* ETA updates or scheduling windows
* Billing clarification or payment links
* Portal access or self-service resources
* Confirmation of resolution

**Best Practice:** Keep SMS conversational, short, and action-oriented.

## 7. Follow-Up Timing & SLAs

Speed matters. Delayed follow-up increases repeat calls and customer frustration.

### Recommended SLAs

* Urgent issues: Same business day
* Standard action items: Within 24 business hours
* Non-urgent informational requests: Within 48 business hours

## 8. Reducing Repeat Calls

Follow-up is successful only if it prevents customers from calling back.

### Best Practices

* Close the loop explicitly (“You’re all set—no further action needed.”)
* Confirm resolution in writing when possible
* Provide a clear next step if additional action is required
* Avoid partial updates that trigger additional inbound calls

## 9. Reporting & Measurement

Follow-up effectiveness should be measurable and transparent.

### Key Metrics

* Follow-up completion rate
* Time to resolution
* Repeat call rate after follow-up
* Conversion rate from follow-up (e.g., bookings via SMS or callback)

## 10. Success Criteria

Follow-up to Avoca-handled calls is successful when:

* Customers do not need to re-contact the branch
* Issues are resolved within expected SLAs
* Context is preserved across touchpoints
* Booking and containment rates improve without increasing branch load