Universal intake

Universal intake that captures every request, by form and by phone

Forms, landing pages, telephony and API come together in one structured intake. Our AI telephony answers 24/7, with provenance and consent captured from the very first moment. Universal across every field and channel.

Talk to us Qualification & verification

GDPR-compliant EU data residency Full audit trail

The intake is the gateway to the entire lead flow. Everything that comes in here determines the quality of what rolls out the other end: whether a buyer receives a clean, auditable request, or a messy record with no provenance. That is why OXIAE treats this gateway as a serious part of the service, not as a simple inbox.

The idea is simple but strict: whether a request comes from a form, streams in via a publisher API or arrives by phone and is answered by our AI telephony, every request follows exactly the same route. Provenance is captured, consent is linked, fields are validated and duplicate requests are filtered out. Only then does a request flow on, normalised, to verification and matching. On this page you will read exactly how a source is connected, which data OXIAE captures and how deduplication works.

Sources that connect seamlessly

Whether a request comes from a form, by phone or via a partner, everything lands in the same structured intake.

Forms

Requests from forms arrive structured right away, with field validation and provenance.

Landing pages

Every landing page delivers into the same intake, regardless of domain or campaign.

Telephony

Phone requests slot seamlessly into the same flow as digital leads, provenance included.

AI telephony

Our AI telephony answers inbound calls 24/7, qualifies the request and delivers it structured into the same intake.

API & webhooks

Connect external systems in real time through a clear API and receive requests without an intermediate step.

Publishers

Deliveries from publishers and partners are recognised per source and assigned cleanly.

How to connect a source

Connecting a new source does not require a complicated migration project. Pick the method that suits your operation: every route delivers into the same structured intake.

Form embed

Place the form on your site with a single line of script. Fields, validation and provenance are already built in; you only choose the campaign and the label.

Landing page

Use a hosted landing page on your own domain. Requests flow straight through, including UTM parameters and the recorded consent text.

API key + webhook

Generate an API key and configure your webhook endpoint. External systems deliver in real time and immediately receive a normalised response with lead ID and status.

Publisher portal

Give your publishers access to the portal. Every delivery is linked to their partner ID, so provenance, volume and quality stay traceable per supplier.

What happens on arrival

Every request automatically goes through the same steps, so your data is clean and auditable from second one.

Provenance captured

Source, channel and partner are registered immediately on arrival.

Consent recorded

Consent is linked to the request and stored in an auditable way.

Validation & deduplication

Fields are validated and duplicate requests are filtered out straight away.

Normalisation

Data is made uniform, so every lead shares the same structure.

What is provenance?

Provenance is the full story behind a request: not just who the applicant is, but where the request comes from, by which route and under what consent. Without that story, a lead is just a row of contact details, and in a regulated market that is not enough.

OXIAE captures provenance at the moment of arrival, not after the fact. That means for every request you can demonstrate where it came from, which publisher delivered it and what consent the applicant gave. This makes billing, quality control and compliance, including the audit trail for GDPR, traceable down to the level of a single lead.

Source

Which system or integration delivered the request: form, API, publisher or agent.
Channel

The medium the request arrived through, for example web, telephony or a partner integration.
Partner ID

The unique supplier behind the request, so every delivery stays traceable and billable.
Campaign

The specific campaign or offer the applicant responded to.
UTM parameters

Source, medium, campaign, term and content are stored separately for accurate attribution.
IP & timestamp

The moment of arrival and the IP address, as proof of the actual delivery moment.
Consent reference

The reference to the recorded consent: text, timestamp and the way it was given.

Deduplication, explained

The same applicant often comes in more than once, through two campaigns, two publishers or simply the same form twice. The platform recognises that overlap before the lead flows on.

For every incoming request, the intake computes a set of normalised keys and compares them with requests from a configurable time window, for example the past 30 days. If a key matches an earlier lead within that window, the platform flags the new request as a duplicate. Outside the time window, the same applicant counts again as a new, valid lead. You set the rules yourself.

Email address

Normalised to lowercase, with plus aliases and spaces removed.

Phone number

Converted to E.164 format, so local and international notations are recognised as equal.

Postcode + house number

Combined as a secondary key to find the same applicant behind different address notations.

What happens to a duplicate? It is not thrown away. The request is kept, linked to the original lead and flagged with is_duplicate: true plus a reference to the first record. That way you keep the complete delivery overview, useful for publisher reporting and disputes, while the buyer receives and pays for the same request only once. You decide whether a duplicate may be paid out again, is blocked, or is only logged as evidence.

From payload to normalised lead

Below you see an example of an incoming webhook payload and how that same request looks after intake, cleaned up and enriched with consent and provenance fields.

intake-example.json

POST /v1/intake  (incoming webhook payload)
{
  "first_name": "Sanne",
  "last_name":  "de Vries",
  "email":      "Sanne.deVries+web@example.com",
  "phone":      "06 12 34 56 78",
  "postcode":   "1011 AB",
  "house_no":   "12",
  "consent": {
    "given": true,
    "text":  "I consent to being called about this offer.",
    "ts":    "2026-03-12T09:41:07+01:00"
  },
  "utm": { "source": "google", "medium": "cpc", "campaign": "solar-panels-q1" },
  "partner_id": "pub_8842",
  "campaign":   "solar-panels-quote"
}

--> normalised lead schema (after intake)
{
  "lead_id": "ld_01HF9Q2K7M",
  "status":  "accepted",
  "contact": {
    "first_name": "Sanne",
    "last_name":  "de Vries",
    "email":      "sanne.devries@example.com",
    "phone":      "+31612345678",
    "postcode":   "1011AB",
    "house_no":   "12"
  },
  "consent": {
    "given":     true,
    "text":      "I consent to being called about this offer.",
    "captured_at": "2026-03-12T09:41:07+01:00",
    "reference":   "cns_4f7a91"
  },
  "provenance": {
    "source":     "publisher",
    "channel":    "web",
    "partner_id": "pub_8842",
    "campaign":   "solar-panels-quote",
    "utm":        { "source": "google", "medium": "cpc", "campaign": "solar-panels-q1" },
    "ip":         "145.97.x.x",
    "received":   "2026-03-12T09:41:08+01:00"
  },
  "dedupe": { "is_duplicate": false, "matched_lead_id": null }
}

Why intake at OXIAE makes the difference

A good intake is more than receiving data. It determines whether the rest of the chain (verification and matching) can rest on a clean, auditable foundation, or runs into mess every day.

One structured flow

Every source comes together in the same intake, with no loose exports or fragmented data.

Auditable from the start

Provenance and consent are captured from the very first moment and always traceable: GDPR compliant.

Ready for matching

Normalised, verified requests flow cleanly through to distribution and routing.

Frequently asked questions about intake

The questions we get most often about connecting sources, provenance and deduplication.

How quickly can I connect a new source?

A form embed or hosted landing page goes live within minutes. An API integration with a webhook endpoint is usually working within one business day, depending on your own system. The publisher portal is available immediately once you invite a publisher.

Which fields are required for a request?

The minimum set is a contact detail (email or phone) plus recorded consent. Beyond that the platform validates whatever you deliver. If required provenance or consent is missing, the request is rejected with a clear error message, so no incomplete lead flows through.

What exactly does OXIAE capture as provenance?

For every request the platform stores source, channel, partner ID, campaign, the individual UTM parameters, the IP address with timestamp and a reference to the recorded consent. Together these form the traceable context behind the lead: the basis of your audit trail.

How does deduplication work exactly?

The platform computes normalised keys on email address, phone number (E.164) and the combination of postcode plus house number. If a key matches an earlier lead within the time window you configure, the request is flagged as a duplicate and linked to the original.

What happens to a duplicate?

A duplicate is not deleted, but kept and linked to the original lead with a reference and the is_duplicate flag. You decide whether it may be paid out again, is blocked, or is only logged as evidence for reporting and disputes.

How do phone requests come in?

Our AI telephony answers inbound calls 24/7, qualifies the caller and delivers the call structured into the same intake as a form, with the same validation, provenance capture and deduplication. Phone and digital come together in one flow.

One clean inflow

What a structured intake delivers

shared flow for every source

provenance fields per request

30 days

configurable deduplication window

100%

requests with consent captured

Capture every request cleanly

Talk to us and see how one structured intake delivers provenance, consent and deduplication as standard, by form and by phone.

Talk to us Log in