DEV Community

Xianghua Feng
Xianghua Feng

Posted on AI-assisted

Who called me about AI training? A minimal intake record for unsolicited meeting requests

“Who called me about AI training?” can become a surprisingly messy team ticket. A receptionist forwards a number, a colleague adds a suspected vendor, and an optional sales meeting starts to look like an approved training request. A minimal intake record helps stop that drift without building a surveillance file about the caller or your staff.

Affiliation and AI note: This article is website-side editorial material for whocallme.co.uk and promotes that site. AI assisted the writing. The schema below is a proposed manual exercise, not a deployed integration, a tested product feature or a report of calls received by the author.

Start with the source boundary

Our page for 0113 547 0885 contains an imported visitor account of an unsolicited call to a personal mobile. The writer said the caller wanted to arrange a Microsoft Teams meeting about workplace AI training and courses. They did not know how their personal number had been obtained.

The page labels the note Telemarketer. Its original publication date is unknown. The visitor's description of the training invitation is anonymous and has not been verified. It does not establish the caller's employer, the number holder, or how any contact details were acquired; displayed numbers can also be spoofed. A named organisation in the account remains a claim, not a verified supplier record.

That is enough for a discussion of intake design. It is not enough to infer a data breach, declare a named company responsible, or populate an internal vendor database with the organisation as an authenticated sender.

A small schema that resists accidental enrichment

Use this as a worksheet in a blank document. No software installation or live incoming call is needed. Each field answers a different operational question:

Field Purpose What to avoid
contact_channel Distinguish phone, email or other contact Guessing the underlying network
offered_activity Describe the proposed meeting or course Marking it as approved training
organisation_claimed Preserve what was claimed, if needed Treating the value as a verified vendor ID
personal_route_used Record whether a personal contact route was involved Copying the employee's actual mobile into a widely visible ticket
source_kind Separate direct staff account from imported public note Merging the two into “confirmed incident”
original_event_time Hold a time only when known Filling an unknown with page retrieval time
handling_owner Name the internal role responsible for the next decision Broadcasting the request to the whole company
disposition Mark declined, pending review or otherwise handled Using “scammer” as a workflow state

For this public source, the original event time should remain unknown. If your team uses a date for the worksheet exercise, label it as the date of review. Don't backfill the missing incident date just to satisfy a required date field.

Walk through the record without adding a person

In the exercise, offered_activity can say “meeting about workplace AI training”. The personal_route_used value can be “reported yes”. source_kind can say “imported public visitor note; original date unknown”. These are illustrative values derived from the page, not a newly observed incident at your company.

handling_owner should not be filled with a real employee's name for this exercise. Use a role such as training-request reviewer. organisation_claimed can be omitted entirely if the purpose is to test the flow rather than investigate the supplier. A source pointer allows a reviewer to read the original wording when justified.

The distinction matters because an intake process can create new exposure while attempting to solve an old interruption. Copying a personal number, job title, calendar availability and guessed employer into a shared ticket gives the whole team more data than it needs to decline a meeting.

Separate the three decisions

A request can be unwanted without being a security incident. It can concern a useful topic without having been authorised. It can be a genuine sales approach without earning a place on anyone's calendar. Keep those decisions separate.

The intake role decides where the request belongs. A training budget owner decides whether the topic is relevant. A meeting organiser decides whether to issue an invitation through normal company channels. None of those decisions requires the first recipient to reveal colleagues' direct numbers, team structure or current availability during the call.

For a small team, these may be the same person wearing different hats. The separation is logical rather than a requirement to add bureaucracy. A short note stating “no training request raised internally” can be more useful than a page of copied sales dialogue.

Review the record before sharing it

Try a manual review with three questions. Does each asserted fact have a source? Does an unknown remain visibly unknown? Could a colleague handle the request without seeing personal contact details? If any answer is no, remove or relabel the field before sharing.

A number-report search may supply context for a human reviewer, but it should not automatically create a vendor blocklist or a staff-profile enrichment task. The lookup result and the team's own contact event are different evidence objects.

Set access and retention according to your existing workplace policy rather than inventing a universal number of days from this example. The useful artefact is a small, bounded request record: what was offered, where the evidence came from and who can decide its disposition. No meeting has been booked, no caller authenticated and no implementation claimed by writing that record.

Top comments (0)