Your First AI Teammate in Leina: Morning Briefs, Customer Follow-Ups, and Weekly Reports

Concept illustration: scattered sources become three useful deliverables across a working day.

A team’s routine work often starts with collecting information. Preparing for a meeting means opening the calendar and finding the latest notes. Following up with a customer means checking what was agreed and what the CRM already records. Writing a weekly report means gathering updates across several places.

Leina can bring those sources into a task requested in team chat, return the result, and preserve a verified method for the next run. Morning briefs, customer follow-ups, and weekly reports show how the same combination of Apps, work context, and Skills supports different jobs.

In Leina’s app access and security boundaries, we explain the AI teammate direction seen in Muse and Grok Bot, and Leina’s use of authorization and inspectable connection mechanisms. Here, the focus is how that architecture helps your team finish a job.

From connected tools to a team deliverable

Apps provide access to the sources a task needs through OpenConnector. Memory can retain project context, while Skills preserve the steps and checks you want to reuse. Scheduling lets the verified method run at an agreed time.

Team job	Sources to connect	Deliverable
Morning preparation	Calendar and project notes	Meetings, preparation, and open decisions
Customer follow-up	Meeting notes and CRM	A fact-based email draft and proposed next steps
Weekly progress	Project documents and task records	Completed work, blockers, and follow-ups with sources

The three jobs share a pattern: define the goal in chat, let Leina bring together authorized sources, review the deliverable, and preserve the method. Your team’s project names, reporting format, and review rules shape the result.

Create Leina and authorize the needed accounts through Connections. Check the operations in Integrations and the requesting member’s access. The examples below start with drafts; name the approved destination and action when you are ready to write or send. See permissions and data access.

1. A morning brief from your calendar and project notes

A useful morning brief identifies decisions and preparation needed today. It can combine a connected calendar with relevant project documents, provided those Apps support the required reads.

@Leina prepare my morning brief for October 13, 2026, in Asia/Shanghai. Read my connected work calendar and the latest Atlas project notes available to me. List today’s meetings, preparation needed, open decisions, and any scheduling conflicts supported by the records. Include source links or record references. Separate confirmed appointments from suggested actions. State unavailable sources. Return it here; do not change events or send messages.

Check the date, timezone, and which calendar was used. Open the source behind an urgent item. A suggestion based on project notes should remain distinguishable from a confirmed calendar commitment.

Useful result: the team can see what needs preparation and which decisions need a person. If the brief misses important material, correct the source scope before adding more tasks.

2. A customer follow-up draft from meeting notes and CRM

Customer follow-up often requires reading two places: what was discussed, and what the CRM says has already happened. Ask Leina to bring them together for one customer.

@Leina read the October 9, 2026 meeting notes for Northwind and its CRM record available to me. List confirmed commitments, unresolved requests, and proposed next steps. Draft a follow-up email using those facts. Do not invent dates, prices, or promises. Flag disagreements between the sources and include references for each commitment. Return the draft here. Do not send email or update the CRM.

Review the recipient, commitments, and whether a request is still unresolved. If documents disagree, resolve the discrepancy before approving the draft. A proposed action is not a promise already made to the customer.

When ready, issue a separate instruction with the exact recipient and approved text. If a CRM update is also needed, specify its record and fields. The relevant connection must support and allow each action.

Useful result: a person can approve a source-grounded follow-up with fewer gaps to reconstruct. Check the saved record or sent message after execution.

3. A weekly progress report with traceable next steps

A weekly report should make the reporting period and evidence clear. Start from connected project documents and task records, then let the team decide which follow-ups to assign.

@Leina summarize Atlas project progress for October 5–11, 2026, in Asia/Shanghai. Read only the connected project documents and task records available to me. Group the report into completed work, blockers, open decisions, and proposed next steps. Give each item a source reference. Include an owner or due date only when a source confirms it; otherwise mark it unassigned or unknown. Report missing sources separately. Return the draft here; do not create tasks or change documents.

Spot-check completed work, a blocker, and an item near the reporting boundary. Confirm that the sources refer to the same project. A missing task list is not an empty task list.

After review, request a write to a named document or table only if the connection supports it. For an engineering-specific version, see the GitHub-to-Notion weekly report workflow.

Useful result: readers can open the evidence and distinguish recorded progress from suggestions that still need approval.

Turn one reliable task into a recurring team method

Run the chosen task on a small real sample and review a second run with different dates or records. Then save stable rules as a Skill: required Apps, fields, source checks, handling of gaps, and review steps. Keep the changing inputs separate. Follow Use Skills With Leina and the reusable reporting Skill guide.

Scheduling is a separate request. Specify frequency, timezone, reporting window, and delivery conversation. For example, ask for a weekday morning brief at 09:00 Asia/Shanghai, with unavailable sources called out and no calendar changes or messages sent. Verify the actual schedule and its first output.

Leina can retain work context and continue longer or scheduled jobs in the background. Still include the current source and reporting window in each task. A Skill does not grant access; conversational memory does not replace source verification.

Judge the first week by the quality of the handoff

Record the time you spend checking, errors found, missing sources, and whether the output helped the next action. Review plan allowances and usage costs before increasing frequency.

Start with the task whose sources you know best. Create Leina, connect those sources, and request a draft. For the broader business-agent context, read Meta Muse for Small Business and Leina’s team workflow.