A useful customer-facing agent needs more than a contact list. It needs to understand what you sell, which claims it can support, whom it is speaking to, and what it may do on your behalf.

In Allorc, start by creating a role and a project. Add your product context, then open a chat in that project and upload your prospect list. You provide the goal and boundaries; your worker can use the available tools to investigate, communicate, record progress, and arrange follow-ups.

Here is how to prepare that handoff.

1. Create a role with a clear responsibility

Choose Create role in your space and give the role a useful name, such as Customer development lead or Customer success coordinator.

Next, name the project and describe the work. For example:

Develop qualified customer conversations for our product. Understand each prospect's needs, communicate using approved product facts, keep useful notes, and report opportunities that need an owner decision.

Keep related conversations in the same project so they share the relevant context. A new chat inside that project can continue the work without requiring a new role for every prospect.

2. Give the worker reliable product context

During setup, use Add files to upload your reviewed documents. Wait for the files and role preparation to finish before starting the campaign.

Markdown files are a practical choice: they are easy to read, review, and update. You do not need a large document collection. You need enough accurate information for the worker to answer the questions a real customer might ask.

The following filenames are suggestions, not a required Allorc format.

Document	What to include
`PRODUCT_AND_FIT.md`	What the product does, whom it helps, problems it solves, prerequisites, limitations, and situations where it is a poor fit.
`CAPABILITIES_AND_EVIDENCE.md`	Available features, supported integrations, operational limits, approved examples, and evidence for performance or customer-result claims.
`PRICING_AND_TERMS.md`	Current prices, currency, included users or units, billing period, taxes and fees, renewal, cancellation, and who approves exceptions.
`SECURITY_AND_DATA_HANDLING.md`	Approved information about data use, access, hosting, subprocessors, retention, deletion, exports, and security evidence. Mark unanswered questions explicitly.
`ONBOARDING_AND_SUPPORT.md`	Setup requirements, responsibilities, support channels and hours, escalation, and what happens when a customer leaves.
`CUSTOMER_QUESTIONS.md`	Approved answers to recurring questions, source links, known gaps, and the person who can resolve each gap.
`COMMUNICATION_AND_AUTHORITY.md`	Allowed channels, tone, information-sharing boundaries, decisions requiring approval, follow-up limits, and reporting preferences.

Add an effective date or version and a responsible owner to important documents. When terms change, identify the current version and explain what it replaces.

Keep confidential negotiation information separate from customer-shareable material, and check project access before uploading it. A filename marked “private” is not an access control. Connect accounts through the supported integration flow rather than putting passwords or API keys in documents.

Security documentation should describe evidence, not aspirations

If you do not have a certification, signed agreement, confirmed retention policy, or verified security control, leave that fact unresolved. A generated document does not establish that the control exists.

Give the worker an authorized contact for unanswered product and security questions. That makes it possible to obtain a real answer rather than repeat a vague deferral to the customer.

3. Use this prompt to prepare your Markdown files

You can ask ChatGPT or another writing assistant to organize your existing material. Supply your actual product details and sources; a product name alone is not enough.

Copy and adapt this prompt:

Prepare a Markdown knowledge pack for an agent representing my product to
prospects and customers.

Product: [name and current version]
Seller: [company]
Product website: [URL, if available]
Intended customers and problems solved: [details]
Approved source material: [attach documents or provide links]
Current pricing and terms: [details]
Known limitations and security evidence: [details]
Person who can resolve missing facts: [contact or role]

Create separately named Markdown documents covering:
- Product and customer fit
- Capabilities, limitations, and supporting evidence
- Pricing and commercial terms
- Security and data handling
- Onboarding, support, and exit
- Customer questions and approved answers
- Communication boundaries and decision authority

Use supplied evidence and public sources you actually inspect. Identify each
material claim's source and effective date where available. If a source is
unavailable, say so.

Ask focused questions about important gaps. Mark unresolved facts UNKNOWN.
Do not invent features, integrations, certifications, guarantees, customer
results, security controls, or contractual terms. Clearly distinguish current
facts from proposals and illustrative examples.

Separate customer-shareable material from seller-private information.
Do not include credentials or unnecessary personal data.

Finish with the missing evidence and owner decisions needed before outreach.

Review the resulting files before uploading them. Pay particular attention to prices, security statements, delivery promises, and approval authority.

4. Upload your prospects in a project chat

Once the role is ready, open a chat inside the same project and attach your prospect CSV.

Useful columns include:

A stable prospect ID, company name, and company domain.
Contact name, professional role, and the actual destination address.
Existing relationship and relevant conversation notes.
Verified timezone, when known.
Contact source, permitted contact scope, and do-not-contact status.
Last contact date and any existing pause or follow-up agreement.

These are recommended fields, not a mandatory schema. Explain unfamiliar columns and leave unknown facts empty rather than guessing.

Use contacts you are authorized to approach, and include existing opt-outs. Avoid uploading unrelated sensitive information. Having someone's address does not by itself establish permission to contact them.

5. Connect the capabilities the job needs

Before authorizing external work, verify the communication channel and sender account the worker should use. Check the relevant connection permissions and approval settings.

If the job includes future follow-ups, verify that scheduling is available too. Asking for a reminder cannot create a capability or permission that the project does not have.

You can begin with draft-only work or review the first messages before allowing standard outreach. Choose the level of autonomy that matches the responsibility you are delegating.

6. Give the worker a goal and boundaries

You do not need to prescribe every search query or write every message. Give the worker a clear outcome and enough authority to move toward it.

For example:

Use the approved project documents and this prospect list to identify suitable
opportunities and work toward converting qualified prospects into customers.
Understand relevant company context and each person's needs, personalize the
conversation, and adapt to replies.

You may: [choose the actions you authorize].
Use this channel and sender: [account/channel].
Ask me before: [discounts, custom terms, or other commitments].
Follow-up boundaries: [contact hours, frequency, pauses, and when to stop].
Product/security questions go to: [authorized contact].
Report progress: [where and when, or upon meaningful changes].

Keep useful notes, current opportunity status, and the next justified action.
Respect declines and no-contact requests. Tell me what is blocked and what
you need from me. Distinguish interest, acceptance, payment, and activation
using the evidence available.

“Convert these prospects into customers” describes an ambition. It does not grant unlimited contact, pricing authority, or permission to make unsupported commitments. State the boundaries that matter to your business, and use the platform's approval and access settings alongside your instructions.

7. Look for understanding, not just more messages

Useful research answers questions that could change the approach: What does the company do? Which product facts are relevant? What remains unknown about this particular team's needs?

Public information can establish company context. It usually cannot establish a person's private budget, internal approval process, or willingness to buy. Those details come from the conversation or other authorized evidence.

A good customer message uses what is known, answers the actual question, and offers a useful next step. Personalization should change the substance, not just the name in the greeting. If a prospect requests documentation the worker does not have, the next step may be obtaining that evidence from you rather than sending another pitch.

8. Make follow-through visible

Customer work often spans several conversations. Keep it in the relevant project and review the records as it develops.

A useful opportunity record includes the current need, evidence for fit, unanswered questions, the offer actually delivered, the last meaningful contact, and the next action or waiting condition.

Remember the distinctions:

A planned follow-up is not a scheduled reminder.
A scheduled reminder is not a delivered message.
A positive reply is not an accepted order.
An accepted order is not proof of payment or activation.

Future work depends on configured schedules or incoming events. Ask the worker to report any missing capability or unresolved action honestly.

9. Review outcomes and expand deliberately

Start with a small group and inspect factual accuracy, relevance, tone, delivery, and follow-up timing. Correct missing context before expanding.

Ask for reports that separate contacted prospects, qualified opportunities, open questions, delivered offers, acceptance, and any payment or activation supported by receipts. Include declines, opt-outs, pauses, and unresolved work.

The goal is a worker that advances appropriate conversations and keeps you informed. Some prospects will be a poor fit, and some will decline. Accurate decisions and respectful follow-through are part of doing the job well.

Ready to prepare your first role? Get started with Allorc, or explore the User Guide.