What Should Your AI Know Before It Meets Someone?

A visitor asks, “Could you help with a project like mine?” A job title and a list of skills give your AI little to explain. It needs to know whom you help, what you have done, and what you need to understand before talking further.

Prepare that background so your AI can move from introducing you to responding to someone's specific questions. The example and template below will help you assemble your first version.

For what belongs on the page itself, start with the first-profile checklist.

First, who will arrive with which question?

Complete this sentence:

Someone has seen my ______ and wants to know ______ before contacting me.

For example: “Someone has seen my onboarding project and wants to know whether I could help improve their setup flow.” You need to explain your services, your contribution to the project, and what to prepare before discussing a similar need.

Turn a skill label into background that answers questions

“I do UX design” names a field, but does little to answer “How could you help me?” You could expand it like this:

I help small software teams understand a new user's first experience and find confusing parts of setup. My work includes flow maps, key screen designs, and clickable prototypes. Before an initial conversation, I would like to understand the product, the target users, and the step they find hardest to complete.

This sample combines the audience, problem, deliverables, and starting point for a conversation. It gives the AI more specific information to use.

Add work information to Knowledge. Put preferences such as “keep it short” or “use a friendly tone” in persona settings. See the Knowledge tutorial and AI concierge settings.

Project background answers “What did you actually do?”

Choose one project that explains your work. Describe four things: the original problem, your contribution, the reasoning behind important decisions, and the result.

“Redesigned onboarding” could explain where users got stuck, how you changed the form, and why you added a sample workspace. When a visitor asks why you designed it that way, the AI has concrete work to discuss.

A knowledge template you can fill in

Whom I help
I help [people or teams] with [specific problem]. My main areas are [relevant fields].

What I offer
I offer [services or work]. Typical deliverables include [deliverables]. An initial conversation usually starts with [first step].

One specific example
[Project name] addressed [problem]. I was responsible for [specific work]. I chose [approach] because [reason]. The result was [result], and the work is available at [project link].

What to prepare before talking
A useful introduction includes [information you need]. Visitors can contact me through [contact route].

What needs further discussion
For [cost, availability, scope, or other matters], I would first like to understand [necessary information] before confirming with the visitor. What I can share now is [confirmed information].

For a project without a public link, you can begin with its background and your contribution.

Check the answers in a visitor's words

After filling it in, try asking:

• “What work have you done that relates to our problem?”
• “What was your own responsibility on that project?”
• “What should I prepare before contacting you?”
• “Can you start next Monday, and how much would it cost?”

If an answer is vague, add the relevant background. If it does not explain a point clearly, revise the information and try again. See the test and refine workflow. The full conversation example also follows the journey from project questions to owner involvement.

When your AI can introduce your work, explain a project, and help a visitor understand how to continue, follow the publishing and sharing tutorial and let it start welcoming visitors.