Slack, Calendar, Voice, and Text Capture

Not every open loop starts in email.

Vortyx also supports selected Slack capture, calendar scheduling, voice capture, text capture, and recurring commitments.

The key distinction:

Signals enter through capture and analysis.
Vortyx helps act through review, follow-up, scheduling, and tracking.

Slack is an explicit, user-invoked source.

Use Slack with Vortyx when a message or thread contains:

• a follow-up
• a commitment
• a delegated request
• a waiting item
• a promised update
• a decision that needs tracking
• a next step that should not disappear

Vortyx should not be treated as automatically analyzing every Slack conversation in your workspace.

Connect Slack

Open Connections and choose Slack.

Depending on your workspace, you may need to install the Vortyx Slack app, link your Slack identity, or ask a workspace admin to approve the app.

The Slack connection screen shows whether capture and analysis are allowed by your plan.

Available in Slack

Current Slack surfaces:

• Message action: Send to Vortyx
• Thread action: Analyze Thread
• Mention: @Vortyx in channels where the app is added
• Review flow: Needs Review in Vortyx
• Source link: deep link back to Slack

Slack workflows stay explicit and user-invoked.

Send to Vortyx

Use Send to Vortyx when a Slack message contains an open loop.

This is best for a single message with a clear action or commitment.

Examples:

• "Can you send the numbers by Friday?"
• "I'll check with finance and update you."
• "Let's revisit this next week."
• "Waiting on legal before we can ship."

Analyze Thread

Use Analyze Thread when the full thread contains important context.

Thread analysis is useful when the action, owner, or timing is spread across several replies.

Use @Vortyx

Where the app is added, mention @Vortyx in a channel to ask Vortyx to analyze the relevant context.

Example:

@Vortyx capture the follow-ups from this thread

Slack actions create review items that appear in Needs Review. You approve before they become work.

Calendar is primarily an execution and scheduling connection, not the main source of open-loop detection.

Use calendar with Vortyx to:

• check availability
• suggest available action slots
• schedule actions
• create calendar events after user action
• manage calendar-linked action schedules

Supported Calendar Paths

Current calendar paths include:

• Google Calendar connection
• Outlook Calendar connection
• Apple Calendar scheduling on iOS where local calendar access is available

Google Calendar and Outlook Calendar are connected from Connections. Apple Calendar access is handled through the iOS device permission flow when scheduling locally.

What Calendar Does

Vortyx uses connected calendars for availability checks and user-approved scheduling.

From an Action Detail or scheduling flow, you may be able to:

• connect or reconnect a calendar
• suggest available slots
• set duration before scheduling
• choose a time
• schedule to calendar
• manage an existing calendar schedule
• remove a calendar link

Creating a calendar event is an action. It happens after user intent or approval.

What Calendar Does Not Do

Calendar connection does not mean every calendar event becomes a Vortyx action.

Do not assume:

• meetings automatically become commitments
• every event becomes tracked work
• event attendance means an item is handled
• deleting an event deletes a recurring commitment

Calendar is best understood as scheduling support for work Vortyx already knows about.

Use voice when it is faster to speak than type.

Voice capture is useful for:

• promises made during calls
• next steps after meetings
• follow-ups you remember away from your desk
• waiting items
• recurring responsibilities
• quick thoughts that need review

Example:

I need to send Ananya the revised onboarding plan by Thursday.

After capture, Vortyx can create reviewable suggestions. Review them before saving or tracking.

Some voice capture flows provide realtime transcription and preview. Longer or batch-style capture may process after recording. Available limits depend on your plan.

Use text when you want precision or when speaking aloud is not convenient.

Text capture is useful for:

• short commitments
• exact wording
• multiple next steps
• clarifications
• notes that need structured follow-through

Example:

Waiting for the client to approve the proposal by Friday; follow up Monday if there is no response.

Text capture and voice capture follow the same review-first model.

Use Save for later when the thought matters but does not need full structuring immediately.

This is useful for:

• incomplete thoughts
• rough notes
• ideas that may become work
• future review

If something has a clear owner, action, or timing, use voice or text capture and review the extracted items.

Use recurring commitments for responsibilities that return on a schedule.

Examples:

• review invoices every Monday
• send the customer update every Friday
• check open support escalations every morning
• review renewal risk monthly

Recurring commitments are different from one-off reminders. They create repeated cycles that can stay visible until the active cycle is completed, skipped, paused, or updated.

• Use Slack for selected messages and threads, not broad monitoring.
• Use calendar for scheduling known work, not as an action detector.
• Use voice when speed matters.
• Use text when precision matters.
• Include owner, action, and timing when you capture.
• Use recurring commitments for repeated operational responsibilities.
• Review suggestions before tracking.
• Mark handled when the work is complete.