Back to My Account

Your communications

Everything Camden sends you about a service you use, in one place. Some of it you can stop. Some of it you cannot, because we are required to send it.

Warning 5 of these cannot reach you at the moment.

How you prefer to be contacted

Council Tax

Council Tax bills and recovery notices

Always sent Post

Your bill, payment reminders and any recovery action.

We use post because this is not available by text message. You did not choose this.

Council Tax set this up for you.

Tell me when my new bill is ready

You can stop these Email Action required

A short message when a new bill is published in your account.

We use email because we could not use text message for you. You did not choose this.

We do not have a confirmed email address to send this to.

Direct Debit reminders

You can stop these Email Action required

A reminder a few days before we collect a payment.

We do not have a confirmed email address to send this to.

Council Tax support and discounts

You can stop these Email Action required

Reductions and discounts you might be able to claim.

We do not have a confirmed email address to send this to.

Libraries

Camden libraries newsletter

You can stop these Email Action required

Events, activities and what is on at your library.

We do not have a confirmed email address to send this to.

Highways

Roadworks and disruption near me

You can stop these Email Action required

Planned works and closures affecting one of your addresses.

We use email because we could not use text message for you. You did not choose this.

We do not have a confirmed email address to send this to.

More you can sign up for

Leisure centre offers

Leisure · Email or Text message

Membership offers and promotions at Camden leisure centres.

Recycling and collection changes

Waste and recycling · Email or Text message

Changes to collection days, including over bank holidays.

Some communications are set up by a service rather than chosen by you, and some are not offered here at all. Whether those should look any different from the ones you chose is unresolved — see §7 of docs/profile-communication-subscriptions.md.

Behind the scenes

Property names follow docs/profile-communication-subscriptions.md, which says its own spelling is illustrative. The shape is what was decided.

Usable destinations

email: no usable destination
sms: no usable destination
post: usable
in-app: usable

Seeded by seedChannel() against this fixture — §4.1, the one communication rule with real logic behind it here.

Subscriptions

subscriptionId: sub-ct-billing
catalogueTopicId: council-tax.billing-and-recovery
state: active
basisAtOptIn: statutory
noticeVersionAgreed: — nothing was agreed
channel: post
channelSource: catalogue-fallback
createdBy: Service
captureChannel: service-api
createdAt: 2026-06-29T08:02:00Z
context: {"originatingService":"council-tax","accountReference":"CT-4471902"}
deliveryIssue: none

subscriptionId: sub-ct-bill-ready
catalogueTopicId: council-tax.bill-ready-alert
state: active
basisAtOptIn: public-task
noticeVersionAgreed: v1
channel: email
channelSource: catalogue-fallback
createdBy: Citizen
captureChannel: my-account
createdAt: 2026-07-02T09:20:00Z
deliveryIssue: We do not have a confirmed email address to send this to.

subscriptionId: sub-ct-direct-debit
catalogueTopicId: council-tax.direct-debit-reminder
state: active
basisAtOptIn: public-task
noticeVersionAgreed: v1
channel: email
channelSource: explicit
createdBy: Citizen
captureChannel: my-account
createdAt: 2026-07-02T09:21:00Z
deliveryIssue: We do not have a confirmed email address to send this to.

subscriptionId: sub-ct-support
catalogueTopicId: council-tax.support-and-discounts
state: active
basisAtOptIn: consent
noticeVersionAgreed: v2
channel: email
channelSource: explicit
createdBy: Citizen
captureChannel: my-account
createdAt: 2026-07-02T09:22:00Z
deliveryIssue: We do not have a confirmed email address to send this to.

subscriptionId: sub-libraries
catalogueTopicId: libraries.newsletter
state: active
basisAtOptIn: consent
noticeVersionAgreed: v3
channel: email
channelSource: explicit
createdBy: Citizen
captureChannel: my-account
createdAt: 2026-07-14T18:40:00Z
deliveryIssue: We do not have a confirmed email address to send this to.

subscriptionId: sub-highways
catalogueTopicId: highways.local-disruption
state: active
basisAtOptIn: public-task
noticeVersionAgreed: v1
channel: email
channelSource: catalogue-fallback
createdBy: Citizen
captureChannel: my-account
createdAt: 2026-07-20T11:05:00Z
context: {"scope":"address","addressValueId":"ad-ctax"}
deliveryIssue: We do not have a confirmed email address to send this to.

Not modelled

Expiry, withdrawal history and officer-captured consent. Examples 6.3, 6.6, 6.7 and 6.8 are not fixtures, so nothing renders them.
What happens to a Subscription when the contact value it depends on is removed. Phase 1 sends to the primary confirmed destination for the channel, so there are no per-Subscription pointers to repair.
The material-change flow that forces re-opt-in. §5 lists the event; no owner and no journey exist for it.