Codex

    Core Workflow

    Use Codex playbooks to standardize strategy and guide Lumo recommendations.

    By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20268 min read

    What Is Routine?

    Routine is Lumenbase's playbook layer for repeatable AI-guided execution. It lets teams define strategic context and operational patterns that Lumo uses for Feed recommendations, task execution, and team alignment.

    Instead of ad-hoc instructions, Routine centralizes how your team wants actions framed, prioritized, and executed. The same contact can receive different recommendations depending on which Routine is applied to the list they belong to.

    Routine improves consistency: similar situations produce similarly high-quality next actions.

    How to Create a Routine

    Open Lists → Routines and click Create Routine. A dialog opens with three creation modes:

    Create Routine dialog: choose your creation mode
    Create Routine

    Choose how to create your Routine. Lumo recommends and drafts. You send every message.

    Or start from a template

    • 1
      Sandbox: Write the full instructions yourself. Best for teams who know exactly what they want.
    • 2
      Co-create with Lumo: Answer guided questions; AI structures your answers into Routine instructions.
    • 3
      Templates: Start from pre-built patterns (nurture, re-activation, champion expansion) and customize.

    Creation modes

    ModeHow it worksBest for
    SandboxYou write the full instructions using the standard section structure (Situation, Objective, Prioritization, Cadence, etc.)Teams who know exactly what they want; full control over wording
    Co-create with LumoAnswer questions one by one. Lumo structures your answers into Routine instructions. You can edit the result.Quick setup; good starting point that you refine later
    TemplateStart from a pre-built template (e.g. Qualify & Book a Call, Product Testing Pilot). Customize to fit.Common patterns like qualification, product trials, nurture, re-activation

    Routine card (after creation)

    Once created, each Routine appears as a card on the Routine page. Link it to Lists so contacts on those lists receive recommendations shaped by that Routine.

    Routine card in the list
    Enterprise Nurture

    Focus on enterprise expansion. Champion-led deals. Tone: consultative. Qualify on budget cycle...

    2 Lists
     Updated 2 days ago
    • 1
      Routine name: Click to open and edit. Use the menu for duplicate, delete.
    • 2
      AI context snippet: Preview of the strategic context the AI uses for recommendations.
    • 3
      Linked lists: Contacts on these lists receive recommendations shaped by this Routine.
    • 4
      Last updated: Review and iterate the Routine as your strategy evolves.

    Linking Routine to a List

    Open a List, go to its settings or details, and select a Routine from the dropdown. All contacts on that list will use that Routine's context when appearing in the Feed. A list can only have one Routine linked. See List Segmentation for list setup.

    LinkedIn activity monitoring

    Open a Routine and go to Settings → LinkedIn → Activity monitoring. That switch turns LinkedIn activity syncing on or off for that Routine. When it is on, the Lumenbase browser extension watches LinkedIn for new posts, articles, and shares from contacts on lists linked to this Routine: that membership is the monitored set, anchored in how the Routine is wired to lists (not a separate ad-hoc picker).

    The feature is meant for focused cohorts: keep linked lists to a smaller number of contacts when you care about timely signals. The workspace shows how many contacts are monitored in aggregate across all Routines with monitoring enabled (with a 200 contact guideline before polling quality may spread thin); use multiple Routines or disable monitoring on lower-priority playbooks if you approach that ceiling.

    See LinkedIn Activity, My Connections, and Added Profiles for where those signals surface (record timelines and the Feed).

    Example Routine A vs B: Same Contact, Different Recommendations

    The same contact can get very different recommendations depending on the Routine linked to their list. Here are two contrasting examples for a contact named Sarah Chen (enterprise deal in negotiation, 5 days since last contact).

    Routine A: Aggressive Close

    Routine A: Aggressive Close
    == SITUATION ==
Enterprise deals in late-stage negotiation. Champion identified, contract in review.

== APPROACH ==
Frame outreach around momentum and mutual time-saving. Position yourself as the person who can clear the last blockers and get this closed cleanly.

== OBJECTIVE ==
Close the deal. Move to signature as fast as possible.

== ENGAGEMENT POSTURE & STYLE ==
Direct and urgent. Push for next steps. Include clear CTAs and deadlines.

== CONSTRAINTS ==
Do not suggest long nurturing sequences. Avoid soft check-ins.
    Feed recommendation with Routine A
    SC
    Sarah Chen
    Enterprise License · $45k

    Write email

    Send a deadline-driven follow-up: "Can we get the signed contract by Friday? I can expedite onboarding if we close this week."

    • 1
      Amber accent: Message draft available. Aggressive Routine suggests deadline-driven follow-up.
    • 2
      Recommendation tone: Direct, urgent. "Can we get the signed contract by Friday?"

    Routine B: Consultative Nurture

    Routine B: Consultative Nurture
    == SITUATION ==
Enterprise prospects with champions. Deals may have long decision cycles.

== APPROACH ==
Frame outreach as a peer helping the champion build internal consensus. Position yourself as a resource for their evaluation, not a vendor chasing a signature.

== OBJECTIVE ==
Build trust and support the champion internally. Avoid pressure.

== ENGAGEMENT POSTURE & STYLE ==
Consultative, peer-to-peer. Offer value (case studies, implementation support). No hard deadlines.

== CONSTRAINTS ==
Never push for signature or create artificial urgency. Do not use aggressive CTAs.
    Feed recommendation with Routine B
    SC
    Sarah Chen
    Enterprise License · $45k

    Share a relevant case study or implementation one-pager. Ask if the champion needs any internal-selling support before their next stakeholder meeting.

    • 1
      Blue accent: General action (no draft). Consultative Routine favors supporting the champion.
    • 2
      Recommendation tone: Consultative, no pressure. Case study, one-pager, internal-selling support.

    Same contact, same deal data. Routine A pushes for a close; Routine B focuses on supporting the champion. Choose the Routine that matches how you want to work that segment.

    Where Routine Is Used

    AreaRoutine roleOutcome
    FeedStrategic context for each contact on Routine-linked listsRecommendations and message drafts aligned to the playbook
    TasksRepeatable sequences and operating patternsFaster, less variable follow-through
    Team alignmentStandardizes language and intent across usersLess drift in quality and prioritization
    LinkedIn activity (when enabled)Activity monitoring in Routine settings polls LinkedIn for posts and shares from contacts on that Routine's listsPrioritized social signals without monitoring your entire network

    Building Effective Routine Entries

    What to include

    • Target outcomes (what success looks like).
    • Qualification and prioritization heuristics.
    • Tone and communication constraints for outreach (via your preferred outreach platform).
    • Common objection handling and escalation boundaries.
    • Signals that should trigger immediate action.

    What to avoid

    • Vague goals without concrete action criteria.
    • Conflicting instructions across multiple Routine entries.
    • Outdated strategic assumptions left unreviewed.

    Routine Workflow

    1. Create a Routine (Sandbox, Co-create, or Template).
    2. Define concise context and actionable guardrails.
    3. Link the Routine to Lists (or Lead columns) where it applies.
    4. Contacts on those lists appear in the Feed with shaped recommendations.
    5. Review recommendation quality and iterate the Routine wording as needed.
    Pair Routine with Tasks, Leads, and the Feed to close the strategy-to-execution gap.

    Quick Reference

    Open Routine: Lists → Routines
    Create entry: Routine page → New Routine
    Link to List: List settings → select Routine
    LinkedIn monitoring: Routine → Settings → LinkedIn → Activity monitoring
    Use in Feed: Lists with Routine → Feed
    Related: Feed, List Segmentation, Tasks, Leads

    Frequently asked questions

    What does Routine cover?

    Routine explains use routine playbooks to standardize strategy and guide lumo recommendations. with practical setup and workflow guidance for revenue teams.

    Who should read Routine?

    Sales, revenue, and customer success teams should read Routine when they need a clear, implementation-focused workflow in Lumenbase.

    How do I apply Routine in Lumenbase?

    Use the step-by-step guidance in Routine and then apply the same flow directly in your workspace with your live records and tasks.

    Was this article helpful?