nineAdd Nine to Slack

Explain the invoice.
Move the conversation forward.

Give Nine the customer conversation. It connects the question to the right Stripe records and leaves a useful billing note in Intercom, ready for your team to pick up.

A billing note that moves the conversation forward.

Review this Intercom billing question, find the customer's Stripe subscription and recent invoices, and add a concise billing summary to their Intercom contact.

Illustrative workflow and deliverable.

Nine

Why the invoice increased

The latest invoice reflects a higher seat quantity than the previous period.

Customer question
Why did our latest invoice increase?
Confirmed
The invoice quantity increased from the previous period. The current subscription reflects the higher seat count.
Still to check
Whether the customer intended the seat change.
Next step
Confirm the change before preparing the customer reply.

Supporting context

  • Current invoice
  • Previous invoice
  • Subscription

Illustrative deliverable, for your team’s review.

How Nine gets there.

Find the right customer.

Read the conversation and associated contact, then locate the corresponding Stripe customer.

Clarify an ambiguous match before using the billing records.

Explain what changed.

Compare recent invoices and the subscription, keeping confirmed billing facts separate from open questions.

Attach the relevant record references to the explanation.

Carry the context back.

Save a concise internal note on the Intercom contact, with the next useful check.

Leave the customer response and billing decisions with your team.

The result starts
a conversation.

The billing context is saved with the contact so the support teammate can pick up the conversation.

Jamie

Make the next check clear for the teammate handling the reply.

Nine

The note separates the confirmed seat change from the question still to resolve: whether the customer intended it.

Illustrative follow-up in # customer-support.

Delivery, access, and your team’s role.

Where the work lands

Internal note · Intercom contact

The billing context is saved with the contact so the support teammate can pick up the conversation.

Access needed

Intercom conversation and contact read access, contact-note write access, and Stripe customer, subscription, and invoice read access.

Your team’s part

Your team reviews the note and decides what to say or change.

Share the billing details relevant to the handoff. This example does not issue refunds, change subscriptions, or send a customer message.

What gets easier.

Less tab-to-tab investigation.

Delegate the account lookup and comparison together, rather than assembling the billing context by hand.

Facts the next teammate can use.

Keep the confirmed change, supporting records, and unresolved question in the same contact note.

A clearer next conversation.

Your team starts with the billing context and decides how to respond to the customer.

Before you hand it off.

Does this send a reply or change the subscription?

This workflow creates an internal contact note. Your team reviews the context and owns the customer response, refunds, and subscription decisions.

What if the customer match is unclear?

Nine asks for a reliable identifier rather than treating a possible match as confirmed. Bring the relevant account or customer ID when you have it.

Bring the next billing question.

Tell us where the customer conversation starts and which billing records your team needs. We’ll discuss the result, available actions, and access for that handoff.

Your first
useful handoff.

Join the early-access list. Tell us what you’d like Nine to do and which tools it needs.

Join Nine’s early-access list

No purchase commitment. This joins the list; it doesn’t create an account or book a call.