π§Ύ Overview
This article outlines the key details required to successfully configure a Screenpop integration for a new Evo Voice client, using George Brew as an example. It also clarifies when a voicemail box is needed, how to capture the preferred area code, and why location data is important.
Common question:
What details are needed to complete the setup of a Screenpop for a new client (e.g., George Brew), including whether a voicemail box is required, the preferred area code, and the client's location?
π Required Information for Screenpop Setup
Before Screenpop can be fully configured and tested, gather the following client-specific information:
1. Client's Full Name & Company Name
-
Used for tagging the client in Evo records and endpoints.
-
Example:
-
Name: George Brew
-
Company: Brew Financial LLC
-
2. Preferred Area Code
-
Used when assigning a DID (direct inward dial) number.
-
Important for caller familiarity and regional trust.
Example: Area Code 646 (New York)
β Note: If the preferred area code is unavailable, offer alternatives or waitlist options.
3. Client Location
-
Required for:
-
DID assignment
-
Emergency Services (E911)
-
Regional routing (if applicable)
-
-
Include:
- City, State, and ZIP Code
Example: New York, NY 10001
4. Voicemail Box Required?
-
Confirm if the client wants voicemail on their main line or extension(s).
-
If yes:
-
Assign a voicemail box.
-
Set up voicemail-to-email (optional).
-
Record greeting or upload default.
-
β Best practice: Always clarify whether voicemail is needed for direct lines, team lines, or fallback routing.
5. CRM or App Integration Details (If Available)
-
Which CRM or system should Screenpop open?
- E.g., HubSpot, Salesforce, Clio, Zoho
-
What URL or format should be used?
- Screenpop usually opens a search page or contact profile using the callerβs number.
Provide a sample search URL or contact page structure if possible.
π¦ Optional but Helpful Details
| Item | Why It's Useful |
|---|---|
| Call flow or routing preference | Helps with initial call handling setup |
| Main contact person | For follow-ups and confirmation |
| Internal team directory | For setting up extensions if needed |
| Support hours or availability | Informs routing logic (after-hours flow) |
β Resolution Summary
| Field | Required? | Notes |
|---|---|---|
| Full Name & Company | β | For tagging and endpoint setup |
| Area Code | β | Used for DID assignment |
| Client Location | β | Required for number and E911 |
| Voicemail Box Needed | β | Affects routing and call flow |
| CRM Integration Details | Optional | Enables Screenpop functionality |
π Still Need Help?
If you're unsure which details are missing, please contact Evo Support for assistance.
When reaching out, be sure to include:
-
Company name
-
Desired area code
-
Location info (City, State, ZIP)
-
CRM or screen pop platform (if applicable)
-
Whether voicemail should be enabled
Our support team will guide you through the next steps for proper onboarding or provisioning.