Resolve likely entities
Return a main result when the evidence is good enough, instead of forcing a number-only workflow every time.
QuickContact API helps browser workflows, CRMs, internal tools and operational systems turn a number plus local context into a better contact decision.
{
"rawNumber": "+351 253 601 200",
"captureMode": "EXTENSION",
"sourceType": "TEL_LINK",
"origin": {
"host": "www.uminho.pt",
"title": "Contactos",
"nearHeading": "Academic division"
}
}
Good fit for extensions, operational tooling and CRM plugins that already see the page around the number.
QuickContact prefers a grounded main result plus alternatives instead of pretending weak evidence is enough.
The API is the primary message here. The Android app is available as a separate testing and consumer flow.
QuickContact API combines the number with the surrounding evidence: source host, title, headings, labels, nearby text and other local signals that make contact resolution more reliable.
Return a main result when the evidence is good enough, instead of forcing a number-only workflow every time.
Keep plausible alternatives visible when the page context supports more than one candidate.
Fall back conservatively when the context is weak, missing or inconsistent.
The API is strongest when a number arrives together with local page context from a browser workflow or another source that already understands the surrounding page.
Start from a `tel:` link, tapped number, selected number or a controlled manual input path.
Send title, host, nearby labels, headings and compact excerpts instead of a blind number-only query.
Use retrieval, structural grounding and semantic arbitration to produce a useful primary result.
Consume the main result, alternatives and confidence to drive browser workflows, CRM actions or manual review.
The API is suitable for workflows where a browser or tool already has access to the local page and needs a better entity suggestion than a plain number lookup can provide.
Resolve numbers directly from web pages and offer better save flows without copying information across multiple tools.
Turn inbound or discovered numbers into likely entities with confidence and alternatives before a record is created.
Support back-office teams, research flows and browser-assisted operations with a more reliable contact decision layer.
QuickContact is most useful when the number arrives with the local clues already present in the page or browser flow. That is where better contact resolution actually becomes possible.
You get a primary result, alternatives and a clearer distinction between “strong enough to act” and “not enough evidence yet”.
The public API is aimed at internal tools, browser workflows, CRM plugins and staged partner integrations. Consumer app access is handled separately.
For early prototypes, internal tools and teams validating the workflow.
For browser tools, small commercial teams and lightweight helpdesk flows.
For CRM plugins, internal platforms and early white-label deployments.
Read request, response and auth details for the current public surface.
See the current cautious public status surface for uptime and operational expectations.
Review the current prelaunch security and privacy posture for the API.
QuickContact for Android is available as a separate testing and consumer flow. Firefox + extension is the recommended path. Manual lookup remains available as fallback.
This homepage now explains the API first. The app remains real and available, but it no longer carries the main message of the site.
Start with docs and pricing, then contact us for pilot access, internal tooling, browser integrations or staged partner deployments.