Bring the right record into the workflow.
Give a company connection a specific job. A connection brief links the required record, its meaning, the people using it and the decision the workflow supports.
Start with the record the task needs.
A quotation handoff may need the item specification, quoted unit and delivery basis. The task brief says how those fields support the customer reply. The AI Chief connects the handoff to the team’s goal.
Use approvals for the action that changes a customer commitment. Company knowledge supplies the relevant instructions, and the security page explains information handling on this website.
Write a connection brief a workflow owner can explain.
A Sales Agent needs the current enquiry and quotation. A Procurement Agent needs the requested item and selected supplier terms. Name the actual records and fields for the job.
The dashboard follows the task that uses the information. Alerts bring source questions to their owner, and operations coordinates the handoff affected by the answer.
- 01
1 · Identify the record
Name the item, order, document or event, its source owner and the period it describes. Explain what each selected field means to the task.
- 02
2 · Define the direction
Specify whether the workflow reads selected information or proposes a change. Give each action its own business purpose and authority.
- 03
3 · Name the reviewer
Choose the person who checks the information and the person who approves a consequential action. Keep those roles beside the connection request.
- 04
4 · Plan the source question
Describe how the team handles a waiting record, a changed unit or a version difference. Identify the manual next action and its owner.
- 05
5 · Follow a complete example
Use one source record to walk through the task result, human review and next handoff. Record the access and conditions that example needs.
Connection acceptance questions
Company-tool connections: Coming soon.
A trading company maps a quotation handoff.
A 30-person trading company wants the right quotation fields to reach the salesperson answering a buyer’s specification question. The purchasing manager owns the source terms, and the sales manager reviews the customer response.
- 01
Monday · Choose the fields
The managers select the item description, quoted unit, delivery basis and quotation reference needed by the customer task.
- 02
Tuesday · Confirm their meaning
Purchasing explains the unit and delivery terms. Sales confirms which parts answer the buyer’s actual question.
- 03
Wednesday · Walk through a source gap
The team tests a quotation whose delivery basis needs clarification. The handoff brings the question to the buyer and holds the customer decision for its reviewer.
- 04
Thursday · Check the action boundary
The managers distinguish reading the supplied terms, drafting a reply and approving a changed customer commitment.
- 05
Friday · Record the connection brief
The team lists the selected source fields, their owners, the required access and the next review for the proposed connection.
Give access and business approval their own owners.
Use people in control to describe the authority a task needs. Finance and HR workflows can require their own source owners and audiences.
| Connection concern | AI preparation | Manager or workflow owner | Owner or reserved approver |
|---|---|---|---|
| Read selected source fields | Describe the requested fields and their task purpose | Confirm the source meaning and audience | Approve access reserved by company policy |
| Write or change a record | Draft the proposed change and its effect | Check its business purpose and scope | Authorize consequential or reserved changes |
| Use a result in customer work | Draft the output with the relevant references | Approve the proposed communication within mandate | Approve reserved customer commitments |
| Expand the connection | List the extra fields, users or actions needed | Review the operational need | Decide access beyond delegated authority |
Make the result of the connection discussion concrete.
The brief names the source, selected fields, allowed direction, intended users, reviewer and follow-up method. Keep a worked example beside that list so the receiving team can explain how the record becomes a useful result.
The company-context form displays your company name, email, size and industry in the browser. Use those basics alongside a process description when discussing a first connection.
Choose a connection around one company process.
The product overview follows the goal-to-task loop. A trading team may begin with a quotation handoff; a services team may begin with a client scope document.
Use the working guides to describe the process and compare plan scopes around the people and responsibilities involved.
Questions, answered.
What belongs in a connection brief?
The source record, selected fields, their meaning, the required access, the users and the reviewer of the resulting work.
How narrow should the first connection be?
Start with one recurring task and the fields needed to complete its handoff.
Who confirms the source meaning?
The person responsible for that business record, working with the manager whose task uses it.
What does the team check in a worked example?
Follow one source record through the output, the review and the next action, including the question raised by a changed or waiting field.