One component, everywhere you build

One Salesforce chat. Right on the record.

Message threads bound to any object, a rich publisher with @mentions, inbound and outbound bubbles, and date breaks between days. On Lightning pages and in your own LWC, configured with clicks. No code.

Start free Explore the documentation

@

mentions built in

Rich

or plain publisher

0

lines of Apex

What it does

A conversation your users can actually take part in

This is the component in action. Read the thread, drop in a message, mention a teammate, and let the dates sort themselves.

CS

Case #00042

Escalations

Today

The customer says the export still times out on large orgs.

Thanks. @Priya can you check the batch size on their instance?

On it. I will post the results here once the job finishes.

@

Write a reply...

Send

Same component, every surface

One chat. Two ways to ship it.

The same thread and publisher, whether an admin drops it on a page or a developer puts it in their own markup.

Lightning pages

On a record or app page

Build it visually with the dcChat component in Dynamic Components, point it at any object with a no-code query, and drop the result onto any Lightning page in App Builder.

Dynamic Components

LWC / code

In your own component

Developers drop avonni-dd-chat straight into an LWC template with documented attributes and a publish event. Same chat, in the markup you already own.

Where teams use it

Built for the conversations that live on your records

Customer replied

Logged to the case

Case comments that write back

Give agents a real thread on the case record instead of a flat activity log. Every reply saves straight to Salesforce.

@Sam take a look

On it now

Internal notes on any object

Drop a chat on an opportunity or account so the team can talk in context, with @mentions to pull people in.

9:02 Order placed

9:14 Shipped

Message history from your data

Point the chat at a message object with a no-code query and render the whole conversation, ordered by date, no Apex.

A chat that belongs on the record, not in a tab

A plain related list can show messages. It can't let people mention a teammate, post rich replies, or break the thread up by day. This one does, out of the box.

@

mentions to pull people in

Rich

text or plain, your choice

Any

object, through a no-code query

Questions

Chat, answered

Which package is the Chat in?

The Lightning-page version ships in Dynamic Components, and the same chat is available as an LWC in LWC Components. One subscription covers both.

Which Salesforce objects does it work with?

Any standard or custom object. Point the thread at a message or comment object through a no-code query, and it renders each message in order.

Do messages save back to Salesforce?

Yes. The publisher fires an event with the message, the author, and any mentions, so your Flow or component writes it straight to the record.

Can important messages stay at the top?

Yes. Turn on pinning and users pin messages from the message menu into a banner above the thread. Click a pin to jump straight back to the message.

Can it connect to Agentforce?

Yes. Alongside the standard chat, Dynamic Components includes an Agentforce chat that runs a conversation against a Salesforce agent.

Do I need Apex or custom code?

No. Admins configure the chat with clicks in Dynamic Components. Developers who prefer code can use the LWC version with documented attributes.

Something missing on the Chat component? Users ask, we ship. See what shipped →

Put Chat on your records

Install free from the AppExchange and add a real conversation to your first record page today. Talk to us when you are ready to scale.

Start free Talk to sales