Sales & business developmentResearch and qualify a lead batch
A sourced shortlist with fit reasons and verified contact candidates.
Give it this job ↗What a good result includes
- Source each company fact.
- Candidate email is not a verified recipient.
- Label ranking as a supplied business-fit rubric.
Create a tailored prospect page
A private branded page ready for employee review.
Give it this job ↗What a good result includes
- No invented logos, relationship, metrics or endorsements.
- Keep private account notes out of prospect copy.
- Verify artifact ID and saved revision.
Update the CRM after a conversation
The right contact or deal has the next step, owner and date.
Give it this job ↗What a good result includes
- Retain record ID and provider receipt.
- Do not change deal stage without evidence or an explicit instruction.
- A saved draft is not an updated CRM.
Send a researched follow-up
One authorized message sent to the confirmed business recipient.
Give it this job ↗What a good result includes
- Do not infer permission for a broad campaign.
- Keep uncertain sends out of automatic retries.
- Do not count a send as a reply or conversion.
Investigate and answer a ticket
A grounded customer reply saved to the correct ticket.
Give it this job ↗What a good result includes
- No invented root cause or resolution.
- Never request a password.
- Distinguish an internal note from a public reply.
Prepare and file an engineering escalation
A linked engineering issue with facts and reproduction details.
Give it this job ↗What a good result includes
- No duplicate escalation.
- Do not claim a fix timeline.
- Keep customer-private details within the approved destination.
Turn a resolved pattern into documentation
A source-backed knowledge draft saved in the knowledge system.
Give it this job ↗What a good result includes
- Do not infer a confirmed resolution from an open ticket.
- Cite guide and ticket references privately.
- Verify saved text and destination.
Review recurring support issues
A weekly pattern report with evidence and practical proposed fixes.
Give it this job ↗What a good result includes
- Publish denominators and unresolved counts.
- Never count an open ticket as resolved.
- Label suggested changes as proposals.
Build and save a customer onboarding plan
An owned checklist in the team’s project tool.
Give it this job ↗What a good result includes
- Separate promised scope from suggested work.
- Never infer completion from a meeting invitation.
- Keep unknown owners explicit.
Prepare a renewal brief
A brief grounded in commitments, usage evidence and open risks.
Give it this job ↗What a good result includes
- Do not invent usage, pricing or contract terms.
- Separate signals from a risk judgment.
- No commercial commitment without explicit scope.
Send a useful customer check-in
One contextual check-in sent to the agreed recipient.
Give it this job ↗What a good result includes
- Avoid generic check-ins.
- Do not expose internal account assessments.
- Sent is not customer acceptance.
Review accounts awaiting a next step
An exception list and proposed actions with named owners.
Give it this job ↗What a good result includes
- Preserve source account IDs.
- State incomplete pagination or missing fields.
- Do not change stages or owners from a report alone.
Research and write a campaign brief
A sourced audience, message and distribution brief.
Give it this job ↗What a good result includes
- No invented market size or performance.
- Separate research from proposed strategy.
- Use approved brand claims.
Update approved website content
The specified CMS item contains the approved copy.
Give it this job ↗What a good result includes
- Do not publish the entire site by implication.
- Preserve unrelated fields.
- Public release requires a supported, explicitly requested action.
Record and hand off a qualified inbound lead
A contact record and a clear next step for the sales owner.
Give it this job ↗What a good result includes
- Do not invent consent or contact details.
- Avoid duplicate records.
- Retain original lead provenance.
Prepare a campaign performance report
A reconciled report with the actual denominator and clear unknowns.
Give it this job ↗What a good result includes
- No attributed revenue without a stated method.
- Missing cells are not zero.
- State currency, window and definitions.
Turn an incoming request into owned work
A scoped task with the request, owner and completion criteria.
Give it this job ↗What a good result includes
- Do not duplicate an existing request.
- Do not invent a deadline.
- A created task is not completed work.
Write and maintain a working procedure
A saved procedure with steps, owners and exception handling.
Give it this job ↗What a good result includes
- Flag conflicting guidance.
- Retain exceptions and escalation paths.
- Do not grant system access from a procedure.
Follow up on overdue operational work
Verified reminders or task updates within the requested scope.
Give it this job ↗What a good result includes
- No repeated reminder for unchanged work.
- Do not mark an item complete from a reminder.
- Recipient and channel must be confirmed.
Compare vendor options for a work need
A sourced comparison against the company’s requirements.
Give it this job ↗What a good result includes
- No purchase or contract acceptance.
- No invented price or availability.
- Label assumptions.
Write a grounded project status update
A clear update based on actual tasks and changed commitments.
Give it this job ↗What a good result includes
- No completion from a label alone if proof is required.
- Call out missing data.
- Do not invent percent complete.
Create tasks from agreed action items
One verified task per agreed commitment.
Give it this job ↗What a good result includes
- Unknown owner or date stays unknown.
- Do not create duplicates.
- Retain the source meeting reference.
Apply an agreed plan change
Specified dates or owners changed and verified.
Give it this job ↗What a good result includes
- No inferred downstream changes.
- Invalidate a stale plan after a correction.
- Preserve unrelated tasks.
Prepare and save a project handoff
A useful handoff page with decisions, open work and owners.
Give it this job ↗What a good result includes
- No private employee context in shared copy.
- Keep unresolved decisions explicit.
- A handoff page does not prove receipt.
Create a useful engineering issue
A reproducible issue saved in the correct repository or project.
Give it this job ↗What a good result includes
- No invented root cause.
- No code deployment implied.
- Keep customer evidence in its approved scope.
Triage a bounded issue queue
Evidence-based classification and authorized label or owner updates.
Give it this job ↗What a good result includes
- No automatic security severity from insufficient evidence.
- Do not close issues without explicit criteria.
- Do not modify code or merge PRs by implication.
Prepare release notes from completed work
Source-backed notes with changes and known limitations.
Give it this job ↗What a good result includes
- Merged does not mean deployed.
- No invented fixes or performance figures.
- Keep internal security details out of public notes.
Document a known operational procedure
A saved runbook grounded in supplied steps and evidence.
Give it this job ↗What a good result includes
- Do not run arbitrary production commands.
- Flag untested recovery steps.
- No secret values in documentation.
Synthesize a customer feedback batch
A theme report with frequency, source quotes and counterexamples.
Give it this job ↗What a good result includes
- No fabricated quotes.
- Frequency is not market demand.
- Keep private account details out of shared summaries.
Write and save a product specification
A specification with problem, scope and testable acceptance criteria.
Give it this job ↗What a good result includes
- Label open decisions.
- No fictional validation results.
- Keep evidence links accessible to the intended team.
Add agreed work to the backlog
Verified backlog items carrying the agreed requirement.
Give it this job ↗What a good result includes
- No priority changes without a rule.
- No implementation claim from task creation.
- Preserve approved scope.
Prepare a launch readiness review
An evidence-based checklist of ready, blocked and unknown items.
Give it this job ↗What a good result includes
- No launch or deployment from a checklist.
- Unknown is not passed.
- Do not invent readiness percentages.
Reconcile invoices and payments
Exact balances and a source-level discrepancy report.
Give it this job ↗What a good result includes
- Use integer minor currency units.
- Never treat a blank amount as zero.
- No ledger posting or money movement.
Prepare and send an agreed payment reminder
A factual reminder for a verified outstanding invoice.
Give it this job ↗What a good result includes
- No changed terms, late fees or payment commitments.
- Do not send for a paid or ambiguous invoice.
- No financial transaction.
Create review tasks for financial exceptions
Verified review tasks linked to specific discrepancies.
Give it this job ↗What a good result includes
- No automatic accounting correction.
- Do not double-count duplicate payments.
- Do not mark discrepancies resolved from task creation.
Prepare a month-end review pack
A saved checklist and evidence-backed summary for the reviewer.
Give it this job ↗What a good result includes
- No accounting sign-off or ledger posting.
- Use supplied accounting policy.
- Do not invent completion or audited status.
Create an employee onboarding checklist
Verified coordination tasks with owners and agreed dates.
Give it this job ↗What a good result includes
- No autonomous eligibility or employment decisions.
- No system permission grants.
- Do not expose private HR information.
Answer a question from company guidance
A sourced answer with escalation for ambiguity.
Give it this job ↗What a good result includes
- Do not invent company policy.
- Escalate material ambiguity to the owner.
- Keep employee-specific private context private.
Save an approved people-process document
The specified document contains the reviewed procedure.
Give it this job ↗What a good result includes
- No compensation, hiring or termination decision.
- No legal-policy invention.
- No broad audience change by implication.
Track an employee operational request
A bounded task and next step saved for the responsible team.
Give it this job ↗What a good result includes
- Minimize private details in shared tasks.
- No account revocation or employment action.
- A task is not fulfillment.
Coordinate an interview time
A confirmed meeting created after fresh availability and acceptance checks.
Give it this job ↗What a good result includes
- No candidate ranking or selection.
- No fabricated availability.
- Keep scheduling details separate from private assessment.
Send a candidate coordination message
The exact scheduling or status message sent to the confirmed recipient.
Give it this job ↗What a good result includes
- No invented hiring decision or promise.
- No offer terms without explicit supplied approval.
- One confirmed recipient, no broad campaign.
Organize supplied interview notes
A source-faithful private notes summary with decisions left to the team.
Give it this job ↗What a good result includes
- Do not score, rank or select candidates.
- No invented interview quotes.
- Private notes are not shared company memory.
Create recruiting coordination tasks
Verified tasks for agreed interview or candidate follow-ups.
Give it this job ↗What a good result includes
- No hiring or rejection action.
- Keep candidate assessment out of shared task bodies.
- Do not invent a commitment.
Prepare a workday briefing
A concise calendar-and-work brief with useful next decisions.
Give it this job ↗What a good result includes
- No private employee conversations.
- Do not infer a decision from a calendar entry.
- Separate facts from suggested priorities.
Prepare a decision brief
Options, evidence, tradeoffs and explicitly unresolved questions.
Give it this job ↗What a good result includes
- No invented consensus or approval.
- Label assumptions.
- Do not commit budget, contracts or employment actions.
Turn meeting commitments into follow-through
Verified project tasks for the commitments actually made.
Give it this job ↗What a good result includes
- Preserve unknown owners.
- No duplicate task.
- Do not mark agreed work complete from task creation.
Prepare a weekly operating review
An evidence-backed report of outcomes, exceptions and next decisions.
Give it this job ↗What a good result includes
- No invented metrics or productivity gains.
- State missing coverage.
- Recurring execution requires a saved schedule.
No matching work yet. Try another phrase or ask Daywing in chat.
These recipes share the agent’s workflow catalog. They guide the work; available actions depend on your connected account. View current workflow validation ↗
daywing