> ## Documentation Index
> Fetch the complete documentation index at: https://docs.holace.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Communications Tab

> The per-Journey log of calls, emails, and meetings with adjusters and providers — currently a placeholder, shipping as the comms thread feature lands.

The **Communications** tab — labeled **Comms** in the Journey tab strip — is the planned per-case log of every conversation with the carrier, adjuster, providers, and other outside parties. It's the thread of "who said what, when, and on which channel" on a single Journey.

<Warning>
  The Comms tab is currently a placeholder in production. The live tab renders a single message — *"Communications log coming soon. Track calls, emails, and meetings with adjusters and providers"* — until the underlying log is wired in. The feature is on the roadmap; the tab is reserved so its position in the nav doesn't shift when it ships.
</Warning>

\[Screenshot: Communications tab as it appears today — a single centered card reading "Communications log coming soon" with the supporting tagline]

## What it will do

When the feature lands, the Comms tab will be the journey-scoped equivalent of an email + call thread:

<Steps>
  <Step title="Read the timeline">
    Every call, email, and meeting logged against this Journey, in chronological order, with who-on-our-side and who-on-their-side, the channel (phone, email, in-person, video), and a short summary or full transcript when available.
  </Step>

  <Step title="Compose a new entry">
    Log a phone call after the fact, draft and send an email to the adjuster from inside HoLaCe, or record a meeting summary. Entries automatically tag the Journey and surface in the [Notes / Activity](/case-management/journey-tabs/notes-activity) feed.
  </Step>

  <Step title="Attach to a contact">
    Each entry links to the adjuster, provider, or other [Contact](/case-management/journey-tabs/contacts) it's about — so the same thread is visible from the contact's record across every Journey they touch.
  </Step>
</Steps>

## What lives elsewhere today

While the dedicated Comms tab is in flight, comms-adjacent functionality already exists on the Journey:

* **Internal team notes and audit-trail entries** — see [Notes / Activity](/case-management/journey-tabs/notes-activity).
* **Adjuster info** — carrier name, adjuster name, phone, email — see the [Demand](/case-management/journey-tabs/demand) tab.
* **Provider info and contact records** — the [Contacts](/case-management/journey-tabs/contacts) tab holds adjusters and medical providers as first-class contacts.
* **Outbound demand-letter sends** — tracked on the [Demand Letters](/case-management/journey-tabs/demand-letters) tab.

\[Screenshot: A Journey's Notes / Activity feed with an entry reading "Spoke with adjuster, requested 14-day extension" — the kind of entry the Comms tab will eventually structure into a first-class call log]

## What to expect when it ships

The first Comms-tab cut will likely focus on:

1. Manual call/meeting logging (paralegal types in a summary; date/time/parties auto-fill)
2. Inbound and outbound email capture against a Journey-scoped firm address
3. Contact-linked thread view so you can see the same thread on the contact and on the Journey

Voice transcription, two-way SMS, and AI summarization of long threads are listed in firm-side roadmap discussions but aren't dated yet.

## Where to go next

<CardGroup cols={2}>
  <Card title="Notes / Activity Tab" icon="sticky-note" href="/case-management/journey-tabs/notes-activity">
    Today's audit trail — manual notes and system events on the Journey.
  </Card>

  <Card title="Contacts Tab" icon="users" href="/case-management/journey-tabs/contacts">
    Adjusters and providers as first-class contacts that comms entries will link to.
  </Card>
</CardGroup>