Evo Voice allows for flexible delivery of call recordings and transcriptions depending on the business or client’s preference. Here's how it works:
1. Default Behavior – Sent After Every Call
By default, call recordings and transcriptions (if enabled) are:
-
Processed immediately after each call ends.
-
Delivered automatically via email or webhooks, depending on the configuration.
-
This ensures that clients receive real-time access to their call data — useful for support follow-up, compliance, or internal documentation.
2. Can We Send Them as a Summary (e.g., Every Two Weeks)?
Yes, this is possible — but it requires a custom setup. Evo Voice does not send call summaries or batch recordings/transcriptions every two weeks by default, but you can configure this behavior using the following options:
🛠 Option A: Scheduled Email Reports (Custom)
-
You can request Evo Tech to set up a scheduled export or summary delivery.
-
Reports can include:
-
A list of calls,
-
Links to the recordings/transcriptions,
-
Filtered by date range (e.g., last 2 weeks).
-
-
This can be set to go out automatically (e.g., biweekly).
🛠 Option B: Portal Access with On-Demand Review
-
Instead of sending individual call data or summaries, some clients prefer to log in to the Evo Voice portal where they can:
-
View all call logs,
-
Listen to recordings,
-
Download transcripts as needed.
-
-
This avoids inbox clutter while still giving access to full call history.
🛠 Option C: Integration with CRM or Storage Systems
-
If using a CRM or storage platform (e.g., OneDrive, Google Drive, SharePoint), Evo Voice can be integrated to store all recordings/transcriptions automatically.
-
You can then generate summary reports from those platforms on a biweekly schedule.
✅ Recommendation
If you'd prefer to receive a summary every two weeks instead of after every call, contact Evo Support to:
-
Request the setup of a scheduled reporting/export workflow.
-
Specify the format (CSV, email summary, downloadable archive).
-
Indicate which users should receive the summaries and what data to include.