System status
Current state of everything between a prospect filling out a form and a lead arriving on your desk. Maintained by the people who run the programs.
Component status
11 components, from the campaigns that create demand to the screens you sign in to.
-
Operational
Lead generation campaigns
The owned acquisition campaigns that produce demand across all three verticals.
-
Operational
Form capture
Landing pages and forms accepting prospect submissions.
-
Operational
Consent recording
Capture and storage of the disclosure shown, the timestamp, the IP address, and the page.
-
Operational
Filters and validation
Phone validation, duplicate suppression, geography, product fit, and buyer disqualifiers.
-
Operational
HTTP post delivery
Signed posts to buyer endpoints, including the retry schedule.
-
Operational
Webhook delivery
Event delivery for lead lifecycle, credits, and disposition acknowledgements.
-
Operational
AgentTech Dialer delivery
Native delivery into dialer campaigns and disposition feedback coming back.
-
Operational
Solved Enroll delivery
Native delivery into pre-populated client records for buyers in the private beta.
-
Operational
Reporting
Delivery and outcome reporting, program comparison, and scheduled exports.
-
Operational
API
Buyer-facing REST endpoints for leads, deliveries, reports, dispositions, and credits.
-
Operational
Portal
Account sign-in, program configuration screens, and cap and pacing controls.
Delivery components cover the shared paths. If something is wrong with your own endpoint specifically, your account contact tells you directly rather than waiting for a component here to change color.
Scheduled maintenance
No maintenance is scheduled. When work is planned, it is announced here and by email at least 72 hours in advance.
- Outside calling hours. Work that can touch delivery runs when your agents are not on the phone, not when it is convenient for us.
- Leads are held, not dropped. If delivery pauses during a window, leads queue and are released afterward at a pace your endpoint can absorb.
- Not during AEP. No optional maintenance during the Medicare annual enrollment period. Tell us your own peak weeks and we will avoid those too.
- One path at a time. Delivery paths are worked on separately, so a change to the webhook path does not take the HTTP post path with it.
- Emergencies move without notice. Security fixes and upstream failures are announced as incidents rather than as maintenance.
Operating commitments
- 72 hours
- Minimum notice before planned maintenance.
- 60 minutes
- Maximum gap between updates while an incident is open.
- one business day
- First response on a support request.
- One
- Buyer per lead, in an incident and out of one.
How we tell you
Three channels, in the order you will normally hear about something.
Your account contact
A named person rather than a shared queue. Anything affecting your own programs comes from them directly, usually before this page changes.
Email notices
To subscribe, send the addresses you want on the list to contact@solvedmarket.ing. You will get incident notices and maintenance notices, nothing else.
This page
Updated by hand during an incident, then left showing the resolution note until the next change. Bookmark solvedmarket.ing/status.
Reporting a problem we have not posted
Bring these four things and the first reply can contain an answer instead of a question.
Lead id
The lead_id from the payload. One identifier is enough to pull the full delivery record for that lead.
Program
Which program it belongs to, since caps, filters, and delivery paths are all per program.
Timestamp
Time and time zone, or a UTC timestamp. A five-minute window is fine.
Symptom
What you saw: nothing arriving, fields blank, duplicates, a status code your endpoint returned, or a failed API call.
Email contact@solvedmarket.ing or call +1 (866) 415-6192. For anything security related, see the security page.
FAQs
Status questions
How is this page updated?
By hand. When a component is affected, someone changes its status here and publishes the page, so what you read is a statement from the people running the programs rather than the output of a probe. The same update goes to every affected account contact at the same time.
How often will I hear from you during an incident?
At least every 60 minutes while an incident is open, even when the update is that we are still working on it. The final note names the affected components, the window, what changed, and whether any leads were held or delayed.
What happens to my leads during a delivery incident?
They are held, not discarded. Failed deliveries retry on a backoff schedule, and a lead that cannot be delivered after the full schedule is held and is not billed. When delivery is restored, held leads are released at a pace your endpoint can absorb rather than all at once.
When does planned maintenance happen?
In a window outside United States calling hours, announced at least 72 hours in advance. We do not schedule optional maintenance during the Medicare annual enrollment period, and we will avoid your own peak weeks if you tell us when they are.
How do I subscribe to status updates?
Email contact@solvedmarket.ing with the addresses you want on the list. Your named account contact also notifies you directly for anything affecting your own programs, which is faster than any list.
Something is broken but this page says operational. What now?
Tell us rather than waiting for the page to catch up. Email contact@solvedmarket.ing or call +1 (866) 415-6192 with the program, a lead id, and a timestamp, and we can pull the delivery record for that lead.
Something else? Contact us
Seeing something this page is not?
Send a lead id and a timestamp and we will pull the delivery record for it.