Property → person → phone.
Purple3 keeps the property, each person and each individual phone number distinct instead of treating a lead as one flat record.
UNDER THE HOOD
Simple on the screen. A lot happens before Purple3 makes a call.
Purple3 is designed as a controlled outreach operation—not a rogue dialer. Campaign rules, contact state, outreach history, usage and protected safeguards are evaluated before the system decides what can happen next.
Client intent does not bypass system rules. A client can request outreach. Purple3 executes only when the request is permitted.
BEFORE OUTREACH
Every call has to earn authorization.
Purple3 checks the operating rules before an assistant is allowed to act.
Campaign active?→Permitted day?→Permitted time?→Holiday clear?→Contact eligible?→DNC / compliance?→Attempts available?→Usage authorized?→Outreach
If a temporary rule blocks outreach, Purple3 can wait for the next permitted opportunity. If a contact path is prohibited or ineligible, the system blocks it instead of forcing the call.
DURING OUTREACH
The phone call is one event inside a larger system.
Purple3 keeps the contact record, attempt history and conversation outcome connected so the next step is based on what actually happened.
Every number carries its own outcome.
Voicemail, no answer, invalid, DNC, made contact and exhaustion belong to the phone path that produced them.
What was learned stays attached.
Structured outcomes, notes, referrals, callbacks, appointments and conversation history feed the CRM and next-action logic.
Wait when waiting is the right action.
Next-attempt timing and recycle cadence prevent the system from treating “not now” as “never.”
CONTACT INTELLIGENCE
A bad number is not automatically a bad person. A failed person is not automatically a failed property.
PROPERTY123 Main Street
AFTER EVERY INTERACTION
The outcome becomes the next operating decision.
Conversation→Outcome→CRM Update→Contact Status→Action Needed?→Hunt Direction→Next Best Action
THE SYSTEM KEEPS WATCH
Purple3 keeps track of the moving pieces so the operator does not have to.
Campaign state, contact paths, attempts, outcomes, referrals, callbacks, usage and human actions stay connected to the same outreach operation. The radar is not about calling more—it is about knowing what is still active and what needs to happen next.
What should Purple3 do with this contact path?
Keep active. Wait or recycle. Follow a referral. Stop the path. Ask for human review.
What should the operator consider doing next?
Continue outreach, try another number, work another branch, make a human callback, consider mail, re-evaluate the property or review the evidence.
CLIENT CONTROL · PROTECTED BOUNDARIES
You control the volume and operating choices. Purple3 controls the safety rails.
Choose how much outreach you want, when your campaigns are allowed to run, how long they run, how much usage is available and when to pause. Purple3 runs that operation in the background without letting those settings bypass protected rules.
The client can
- Choose and upload leads
- Configure campaign duration and schedule
- Set daily limits and usage
- Pause or resume campaigns
- Request outreach
- Choose which leads to hand off to their CRM
Purple3 will not
- Override a Do Not Call status
- Force calls outside permitted windows
- Ignore protected holiday rules
- Exceed configured attempt limits
- Invent contact eligibility
- Authorize unavailable usage
DESIGNED TO FAIL CLOSED
If Purple3 cannot prove an action is allowed, it should not guess.
Protected decisions are organized around three simple results.
The requested action is permitted now.
The intent is valid, but the action must wait for the next permitted condition or window.
The contact or action is prohibited, exhausted or otherwise ineligible.
RELIABLE PROCESSING
Retries should not create duplicate work.
Purple3 is designed to recognize previously processed events so retries and duplicate system messages do not intentionally create duplicate actions, double-count attempts or repeatedly process the same outcome.
Activity history
Operational events remain visible instead of disappearing into the automation layer.
Conversation history
The operator can see what was said before a callback, appointment or handoff.
Usage records
Usage is checked as an authorization input, not merely counted after the fact.
Auditable changes
Campaign actions, handoffs and important state changes are designed to leave a record.
CONFIGURABLE · NOT HARD-CODED
Purple3 is built around operating rules, not one rigid campaign.
Campaign duration, calling days, hours, timezone, daily volume, attempt limits, usage and follow-up cadence can be configured around the business while protected safeguards remain in place.
THE SYSTEM STILL DEPENDS ON THE INPUTS
Purple3 cannot manufacture a good opportunity from bad lead or contact data.
Lead sourcing and data quality remain the client's responsibility. Purple3 works the information it is given and makes the outreach operation more consistent, organized and visible.
Lead quality
The opportunity has to exist before Purple3 can pursue it.
Skip-trace quality
Better contact data gives the system more real paths to work. Estate & Heir requires relative/associate enrichment.
Human execution
Purple3 can make the connection and handoff. Negotiation, offers, judgment and closing still belong to people.
No guaranteed outcomes. Purple3's job is disciplined outreach, contact intelligence and handoff—not promising that every lead becomes a deal.