Tavina

Contacts tool

๐Ÿ“– This content is synced from the Tavina Handbook.
The canonical version always lives at https://tavina.ai/docs/friendly/tools/contacts

Contacts tool

Tavina’s Contacts tool is an agent-first address book inside the Tavina app. It is the single source of truth for the people you know: names, phone numbers, email addresses, and other ways to reach someone, each with its own consent record, plus tags, lists, custom fields, and a running history for every contact.

In the dev channel, you can manage contacts by hand in the work panel, import them from CSV, vCard, or Google Contacts, watch your Gmail exchanges appear on each person’s timeline, merge duplicates after review, and ask Tavina for help in chat โ€” with Tavina’s own changes kept behind your approval by default.

Use it when contact details are scattered across your phone, your inbox, and old conversations, and you want one place where the people you know โ€” and how you’re allowed to reach them โ€” actually live.

What you can do

The Contacts tool can help you:

  • search, filter, and sort your contacts from the Contacts dashboard;
  • open any contact to view and edit their full record;
  • keep several ways to reach one person โ€” mobile, email, and other channels โ€” tracked separately;
  • record consent per channel, so stopping texts never silently stops emails;
  • organize people with tags and lists;
  • add custom fields for details that matter to you, like a company, a birthday, or how you met;
  • see a history timeline for each contact;
  • import people from a CSV or vCard file with field mapping and a duplicate report;
  • bring in your Google Contacts and, if you choose, push changes you make back to Google;
  • see Gmail activity โ€” messages sent and received โ€” appear automatically on contact timelines;
  • send email to a contact through Postmark or your connected Gmail account, with consent checks, unsubscribe handling, and bounce protection built in;
  • watch a WordPress website for signups, orders, and form submissions, and let them flow into your contacts automatically (dev channel);
  • run tag-triggered email sequences โ€” welcome drips and follow-up series that send themselves on schedule, with exits like an unsubscribe re-checked before every send (dev channel);
  • add Tavina to your iPhone’s own Contacts app as a CardDAV account, read-only, so the people you keep in Tavina show up when you call;
  • review suspected duplicates side by side and merge them in one reviewed step;
  • clean up consent in bulk and export your consent records as proof;
  • ask Tavina to look people up, answer questions about your contact history, and suggest updates โ€” as proposals you approve;
  • turn calls and contact moments into linked Tasks and Calendar follow-ups, and see each relationship’s upcoming, overdue, and completed items in one place.

The Contacts panel

The Contacts tool opens from the toolbar like other Tavina tools. Contacts is a Standard tool, but it is hidden by default on new accounts to keep the first-run toolbar lean; enable it yourself under Settings โ†’ Appearance โ†’ Toolbar โ€” in the Disabled section of the Toolbar settings โ€” with no request or grant needed. The dashboard is your contact list: search by name or detail, filter by tags, lists, or consent state, and sort the list the way you want it.

Opening a contact shows the full contact form. You can edit names and display names, add or update channel identities such as phone numbers and email addresses, assign tags and lists, fill in custom fields, and write notes. Each channel identity carries its own consent state and provenance โ€” where that detail came from and when consent was last recorded โ€” so you always know why a channel is marked the way it is.

Every contact also has a history timeline: a running, per-person record of changes and interactions. Instead of digging through old conversations to remember what happened with someone, open the contact and read the timeline. Gmail activity lands here too, automatically, as described below.

The dashboard also keeps an eye on list health for you: it flags duplicate contacts so you can review them, and it offers consent views for everyone suppressed across all channels or everyone whose consent is still unknown.

Importing from CSV or vCard

The import wizard brings existing contacts into Tavina from standard CSV or vCard files. Imports are sized for personal address books rather than bulk mailing lists in this version.

During import you can:

  • preview the file and map its columns to contact fields โ€” you decide which column becomes which field;
  • mark consent provenance for the details you’re importing, such as which opt-in the file represents;
  • review a duplicate report before anything is saved.

Duplicates are never silently merged. If the importer finds rows that look like the same person โ€” for example, a phone number or email you already have โ€” it reports them so you can decide what to keep. Nothing in your contact list is combined or overwritten behind your back.

Importing from Google Contacts

If your address book lives in Google Contacts, you can bring it into Tavina without exporting a spreadsheet. Connect Google from Settings, then open the Google Contacts card in the Contacts panel to:

  • fetch โ€” Tavina lists your Google contacts and sorts them into what’s new, what matches people you already have, and what looks like a duplicate. Nothing is saved yet; the first pull is a preview.
  • review and import โ€” you choose what to bring in. Imported contacts are marked as coming from Google, so you always know where their details originated. Consent starts as unknown until you set it.
  • refresh later โ€” run a refresh to see what changed on Google’s side: new contacts, changed details, and contacts deleted from Google are all presented for your review before anything changes in Tavina.

The same rule as file imports applies: duplicates are flagged for your decision, never merged automatically.

Staying in sync automatically

Once your Google account is connected and enrolled, Tavina keeps it in sync in the background on a safe repeating schedule โ€” you do not have to keep pressing refresh. Changes you make in your Google account (new contacts, edited details) show up in Tavina on their own.

The same care applies to automatic sync as to everything else in Contacts:

  • if Google and Tavina both changed the same contact detail, that conflict is flagged for your review โ€” one side never silently overwrites the other;
  • if Google expires the saved sync position, Tavina safely re-reads your full contact list; a contact missing from that complete re-read is only unlinked for your review โ€” never deleted from Tavina;
  • your private notes never leave Tavina, and imported changes never change consent settings;
  • deletions still never propagate in either direction.

Managing sync in the Contacts panel

The Contacts panel gives you a Google sync card once your account is connected. It shows the health of your sync at a glance: when it last ran and last succeeded, how many changes are waiting, whether it is paused or backed off after a problem, and whether the Google connection itself needs attention. From the card you can pause and resume sync, run a sync immediately, or detach the account from sync โ€” detaching asks you to confirm first.

When the same contact detail changed on both sides, the card lists each conflict one field at a time: what Tavina has and what Google has, and you choose which value to keep. Nothing is overwritten without your decision. The first setup explains in plain language what will sync and what never will, and it stays off until you turn it on; turning it on once is enough โ€” repeating it does not create duplicates.

The card also includes short setup notes for using Google contacts on Android and iPhone โ€” what a Google account syncs, what stays on the phone or SIM, and what to check so the contacts you keep in Tavina show up in your phone’s dialer.

Pushing changes back to Google

By default, Tavina only reads from Google. It never writes to your Google Contacts.

If you want writes, the Contacts panel has an optional setting, Push changes to Google, and it is off by default. Turned on, contacts you create and edits you make in Tavina also propagate to Google Contacts โ€” this requires trusting the connection at Tavina’s medium trust level, which you grant when you enable it. Two things stay true either way:

  • deletes never propagate โ€” removing a contact in Tavina never removes it on Google;
  • contacts that came from Google are not re-pushed as new creations when you import them.

Adding Tavina to your phone with CardDAV

On an iPhone or iPad, you can add Tavina to your phone’s own Contacts app as a separate CardDAV account. Your phone then shows the people you keep in Tavina โ€” names, phone numbers, email addresses โ€” alongside your other contacts, and keeps them current as they change in Tavina.

This is a Tavina account, not iCloud synchronization, and it lives beside whatever accounts your phone already has:

  • adding it never moves, merges, or copies your existing iCloud or Google contacts, in either direction;
  • it does not replace iCloud or any account you already use โ€” it is one more account your Contacts app can read;
  • because it is read-only (see below), your phone keeps using its normal default account for contacts you create or edit on the phone.

Setting it up

The CardDAV controls live in the Contacts panel, in a CardDAV device sync card next to the Google sync card:

  1. Open the Contacts panel and find the CardDAV device sync card. If CardDAV is off for your account, turn it on from the card.
  2. Add a device โ€” a name like “iPhone” is enough. Tavina creates a username for that device and shows you its password exactly once. Copy the password before you close the pane: Tavina keeps only a hash of it, so it can never be shown again.
  3. On the iPhone, open Settings โ†’ Contacts โ†’ Add Account โ†’ Other โ†’ CardDAV, and enter the server address shown in the card (your Tavina address ending in /v1/contacts/dav/), the device username, and the password you copied. The account is entered by hand โ€” Tavina never installs a profile on your phone.

Each device gets its own username and password. You can keep up to ten devices connected, see when each was last used, regenerate just one device’s password (the old one stops working immediately), or disconnect a device. Disconnecting only stops that one credential โ€” nothing is deleted from Tavina, and the phone’s own contacts are untouched. Turning CardDAV off stops every device at once, just as harmlessly, and you can turn it back on later.

Android phones

The Contacts app on stock Android does not have a native CardDAV account type, and Tavina does not change that. Android users have two supported paths:

  • use the Google sync path described above โ€” import your contacts from Google, and turn on Push changes to Google (off by default) if you also want contacts created in Tavina to reach the phone through your Google account; or
  • install a compatible CardDAV client app, such as DAVx5, and add the account there with the same server address, device username, and one-time password.

What syncs โ€” and what never leaves Tavina

CardDAV sync is currently read-only. Your phone pulls your Tavina contacts and keeps them up to date; anything you edit or create in the phone’s Contacts app does not flow back into Tavina. Writable two-way sync is planned for a later phase. Until then, treat Tavina as the source of truth: make your changes in Tavina and let the phone catch up.

How quickly changes appear depends on the device โ€” phones fetch CardDAV changes on their own schedule, often within minutes, sometimes longer. Opening the Contacts app usually nudges a refresh along.

If you use Google sync as well, the two never fight over the same people: contacts that are actively synced with Google are excluded from the CardDAV account, so your phone does not end up with duplicate contact records.

Before your first device sync, the card shows a short review of what devices will see โ€” any phone number or email address shared by more than one contact is listed for a look before it lands on your phone. Nothing is merged or linked automatically; if you want to tidy those up first, Tavina’s duplicate review is the place.

Two kinds of information never reach the phone at all:

  • your private CRM side of Contacts โ€” notes, relationship history, and consent records stay in Tavina and are excluded from the phone-facing view;
  • call information. Adding the account does not change how calls work: tap-to-call and manual call outcomes (see Calling from the app) are the whole story, and Tavina never reads your phone’s call log or records calls on its own.

Gmail activity on the timeline

When you exchange email with someone in your contacts from your connected Gmail, that exchange shows up on the contact’s timeline by itself: messages sent and received, each with its subject, date, direction, and a one-line summary of what it was about.

Tavina checks for new Gmail activity periodically and whenever you open a contact, so timelines stay current without any effort on your part. Only people already in your contacts appear โ€” Gmail activity matches the email addresses you’ve saved and never creates contacts on its own.

Privacy is the design principle here: Tavina stores only the metadata and the one-line summary โ€” never the message body, and never attachments or raw headers. And when a contact is erased, their Gmail activity is erased along with everything else.

Sending email from Contacts

Contacts can send email for you, with your provider choice and your consent rules doing the gating. Email sending is off until you turn it on.

Choosing a provider

In the Contacts panel, the Email sending setting offers three options:

  • None โ€” the default. Tavina does not send email.
  • Postmark โ€” recommended for real mail: marketing, sequences, and transactional messages.
  • Gmail โ€” for casual personal follow-ups only. Gmail sending is deliberately conservative and cannot carry the unsubscribe headers marketing mail needs.

You also set your sender identity โ€” from name, from address, and reply-to โ€” and the physical mailing address that appears in the footer of marketing email, as commercial mail rules require. Sender addresses that look like no-reply addresses are rejected, because the whole point is that people can answer you.

Postmark credentials are provisioned with operator help and are never entered or stored in the app. Gmail sending uses your connected Gmail account.

How every send stays safe

  • Consent and suppression gate every send. Whether you ask in chat, send from the panel, or an automation fires, Tavina resolves who is on the other end, checks per-channel consent and the suppression list, and refuses fail-closed with a recorded reason when either check fails. Refused sends never reach the provider.
  • Every send or refusal lands on the contact timeline, with the provider, subject, and outcome โ€” so the history of your outreach lives where the rest of the relationship history lives.
  • One-click unsubscribe. Marketing email carries an unsubscribe link. Unsubscribing, a bounced address, a spam complaint, or an unsubscribe or suppression recorded on the Postmark side and reported back by the provider adds the address to the suppression ledger. A provider-side reactivation never lifts suppression on its own; sending again needs fresh, explicit consent โ€” and suppression survives deleting or even erasing the contact, so re-adding someone never resets their opt-out.
  • Gmail is throttled, by design. At most 30 messages per hour, at least 90 seconds apart, at most 150 per day โ€” ceilings Tavina manages for you. You can tighten them, never loosen them. When you ask for more than the limit allows, the extra messages queue and drip out gradually instead of bursting.
  • Marketing mail goes through Postmark only. If a message looks like marketing and Gmail is selected, Tavina refuses it rather than sending mail that cannot honor unsubscribes.
  • Sequences re-check before every step. When a sequence email is due, Tavina re-checks exit rules, consent, and suppression first โ€” a contact who converted, unsubscribed, or was suppressed partway through a sequence never receives the next email.

Asking in chat

You can ask your Tavina agent to email a contact or a group. The agent applies the same consent and suppression checks first, sends through your configured provider, and tells you either what was sent or exactly why it could not be sent.

Email sequences

A sequence is a short series of emails that sends itself on a schedule โ€” a welcome drip for new prospects, a follow-up series after someone reaches out, or a nurture campaign you set up once and let run. Sequences live in the Contacts panel’s Sequences section and run on the same Automations engine as the rest of Tavina’s automations, so there is no second scheduler to keep alive.

Sequences start on their own when a contact:

  • gets a tag โ€” the usual way: tagging someone prospect can start the prospect series;
  • joins a list;
  • matches a segment; or
  • arrives through website intake on the dev channel, when a site is connected.

Each step either sends an email โ€” subject and body with merge fields like first name, full name, and your custom fields, with safe fallbacks when a field is empty โ€” or waits a set number of days. Sequence email is marketing mail, so it goes through Postmark and automatically carries the one-click unsubscribe link and your physical mailing address, the same footers as marketing email you send by hand.

How a contact exits a sequence

Exit rules are re-checked before every single send, not just at enrollment. Tagging someone subscriber, an unsubscribe, a suppression entry, a sequence-specific exit tag, or removing them by hand takes the contact out immediately โ€” someone who converts, opts out, or is suppressed partway through never receives the next email. The consent and suppression checks that gate every send apply to every step of a sequence.

Seeing who is where

Every enrollment is a visible record. Per sequence, the Sequences section shows who is enrolled, which step each contact is on, and when the next email is due. Per contact, a sequences card on the contact’s view shows the same: current sequence and step, next send time, and status โ€” active, completed, exited (with the reason), or paused. While a contact is actively enrolled, re-entry into the same sequence is blocked by default.

Editing a sequence saves a new version. Contacts already moving through it keep the version they started with, unless you explicitly migrate them to the new one.

Pause and safety

  • Pause and kill. Any sequence can be paused and resumed from its card, and a global kill switch stops all sequences at once.
  • Confirmed, recoverable deletes. Deleting a sequence or an enrollment asks for confirmation and can be restored afterwards, like other destructive actions in Contacts.
  • Activation is deliberate. A sequence created from a chat brief starts as a draft, and enrollment is refused until you review and activate it.

You can also ask your agent to do the whole thing conversationally: describe the goal in plain language and Tavina drafts the steps and the copy for your review; once a sequence is live, ask it to enroll or remove people, list who is where, or explain why someone did or didn’t receive a step. Activation and bulk enrollment respect your trust and approval settings.

Bringing a website into Contacts

On the dev channel, Tavina can watch a WordPress website and turn its activity into contact records:

  • new user registrations and profile updates;
  • completed WooCommerce orders and subscription status changes;
  • Fluent Forms submissions;
  • Fluent Community member joins;
  • Tavina subscriber lifecycle events, when the site also runs the Tavina plugin.

New arrivals are matched to existing contacts by email โ€” never silently merged; conflicting duplicates are flagged for your review. Each event can apply tag rules you configure (prospect, subscriber, churned, for example), writes a timeline entry, and can trigger Automations. Marketing consent is recorded only when the website sends explicit opt-in evidence; a signup or purchase alone never implies consent.

Each event type can be switched on or off per site, and deliveries retry automatically with protection against duplicates and replay. Today this runs as an internal dogfood on a small number of sites; operators connect sites using the WordPress Contacts bridge runbook.

Calling from the app

Phone numbers on a contact are now tap-to-call links. Tapping one hands the number to your phone’s dialer โ€” nothing happens automatically beyond that.

Tavina knows a dialer launch is only a request for a call, never proof that anyone answered. So after you tap, a small call outcome form appears: connected, no answer, voicemail, cancelled, or other. You can add when the call happened and how long it lasted, and dictate or type a private note while it’s fresh. Only what you confirm is written to the timeline โ€” nothing is invented.

What you record is saved as a distinct call entry on the contact’s history timeline, kept private to that contact, and never synced outward to Google or other connected accounts. If you close the form without submitting, the draft is kept so you don’t lose your words; submitting twice in a row does nothing the second time.

Because this is a local handoff, Tavina does not read your phone’s native call log, call history, or recordings. Tap-to-call simply connects the address book you keep in Tavina with the dialer you already use.

Contact follow-ups and relationship history

A call that needs a next step, or any contact moment you want to return to, can become a follow-up โ€” a real Task or Calendar event, not a separate to-do list. From a contact’s detail view, or from the call outcome form, choose to add a follow-up: Tavina creates a proper Task (with an optional due date) or Calendar event and links it to that contact.

Linked follow-ups show up where the work lives โ€” the Tasks and Calendar panels โ€” and in the contact’s record, which now gathers the relationship’s upcoming, overdue, and completed items in one place. Completing or rescheduling a follow-up from any panel updates the contact’s history at the same time, so the relationship story stays current without double entry.

Every linked item is written to the contact’s history timeline once โ€” creating it, rescheduling it meaningfully, or finishing it โ€” with who or what made the change and a link back to the item. Deleting or archiving a contact never deletes their follow-ups; those items simply lose their link and stay in Tasks and Calendar, so nothing you scheduled quietly disappears. Private notes stay on the Tavina side and are never written into synced task or calendar descriptions.

Consent per channel

Consent in Contacts is tracked per channel, not per person:

  • someone can opt out of texts while still allowing email;
  • opting a person out of a channel flags that channel on their record โ€” the record itself is kept and marked, never quietly deleted;
  • provenance is recorded with each consent change, so you can see where a consent decision came from and when it was made.

This matters when you ask Tavina to help with outreach: before using a channel, Tavina checks whether that channel is allowed for that person and will not use one that has been opted out.

Consent views, cleanup, and export

Consent isn’t only a per-contact detail โ€” it’s something you can keep healthy across the whole list. The Contacts dashboard offers scope views for exactly that:

  • suppressed everywhere โ€” everyone who is opted out or suppressed on all channels;
  • consent unknown โ€” everyone you’ve never recorded consent for.

From those views you can clean up in bulk โ€” mark a channel opted out or suppressed for a whole group at once โ€” so a stale list never turns into an accidental message.

You can also export your consent records: one contact’s consent history, or the whole registry. The export is your proof-of-consent artifact โ€” a file in JSON or CSV form recording each consent state, when it was recorded, and where it came from. Keep it with your records; it’s what you’d show if you ever needed to prove how someone consented.

Reviewing and merging duplicates

Duplicates happen โ€” the same person once in a CSV import and again from Google, or two entries created months apart. Contacts surfaces candidates for you: pairs of records that share a phone number, an email address, or a similar name, each shown with the evidence that flagged it.

Nothing merges on its own. When you review a pair:

  • you see both records side by side, compared field by field;
  • you choose which record survives and which value to keep for each part โ€” names, channel identities, custom fields, tags, and lists;
  • when you confirm, everything from the duplicate moves onto the surviving contact in a single reviewed step โ€” including the entire history timeline โ€” and the duplicate is retired so it cannot come back as a separate person.

If you picked a value you later regret, the surviving contact is a normal contact: open it and edit it like any other.

By default, Tavina can only propose a merge โ€” the proposal appears in the panel for your approval, like other agent changes. Only when the High Trust direct-update setting is on can Tavina merge directly, and even then every merge is attributed to it.

Tavina’s access to your Contacts

By default, Tavina can read your Contacts to help you in chat, but cannot change them directly.

When Tavina learns something in conversation that should be saved โ€” a new phone number, a correction, a note about someone โ€” the change is prepared as a proposal. Proposals appear in the Contacts panel, where you review them and choose to apply or dismiss them. Nothing from chat touches your contact records until you approve it.

If you prefer direct writes, there is a High Trust setting for exactly that: Allow [your agent’s name] to update Contacts directly. It is off by default. While it is off, every agent change follows the propose-and-approve flow above โ€” including merges.

Asking Tavina in chat

Contacts is built for conversation, not just for the panel:

  • Look people up. Ask “who is Dana?” and Tavina resolves the name against your contacts, asking a clarifying question when several people match.
  • Recall history. Ask “when did I last contact Dana?” and Tavina answers from that contact’s timeline โ€” Gmail activity included.
  • Describe groups naturally. Say “people I haven’t texted in three months” and Tavina can turn that description into a saved segment you can rerun from the panel.
  • Check before sending. When Tavina helps you reach out, it checks per-channel consent first and only uses channels that are allowed for that person.
  • Send the email. Ask Tavina to email a contact: it runs the consent and suppression checks, sends through your configured provider โ€” Postmark or Gmail โ€” and reports the outcome, including why a send was refused.
  • Draft and run email sequences. Describe a sequence in plain language and Tavina drafts the steps and copy for your review; once a sequence is live, it can enroll or remove people, list who is where, and explain a contact’s sequence status.
  • Propose merges. When Tavina spots a likely duplicate, it can propose the merge and wait for your approval in the panel.
  • See who wrote what. When Tavina adds an enrichment note to a contact, the note is attributed to the agent in the panel, so agent-added information is always visible as such.

Deleting versus erasing

Contacts offers two different ways to remove someone, and the difference matters.

Deleting a contact from the panel removes the person from your list, but the record itself is kept: history and consent proofs are retained under Tavina’s retention policy. A delete is the ordinary, reversible-by-policy choice.

Erasing is a separate, deliberate step for explicit erasure requests. When you erase a contact, everything Tavina knows about that person is deleted โ€” identities, custom fields, tags, lists, notes, and the entire history, including Gmail activity. Erasing cannot be undone.

One thing survives erasure on purpose: proof that someone opted out or was suppressed. Those proofs are kept in a minimal form, so if the same person is ever added back, they still cannot be messaged on channels they opted out of. Erasing a contact is not a way to reset consent.

Destructive edits are confirmed and recoverable (tavina/tavina#1955): deleting a tag, list, or segment โ€” or removing a tag, list, or custom field from a contact โ€” asks for your confirmation, is captured to version history before the change, and can be restored exactly as it was. If the capture cannot be completed, nothing is removed. Deleting a contact itself keeps the ordinary soft-delete behavior described above.

Troubleshooting

  • Contacts is missing from the toolbar โ€” it ships hidden by default. Re-enable it from Settings โ†’ Appearance โ†’ Toolbar (Disabled section).
  • An import looked wrong โ€” imports end in a review/report step; check the duplicate report before merging, and ask your agent to list contacts added by that import.
  • Google data looks stale โ€” Google sync is read-only by default and only refreshes when you run a refresh and approve it.
  • Phone edits are not showing up โ€” CardDAV is read-only today; phone-side changes never flow into Tavina.
  • An email did not send โ€” sending is consent-gated and provider-backed (Postmark or Gmail); check the contact’s per-channel consent and your connected provider first.
  • Still stuck? See Getting help and reporting bugs โ€” the in-app Help tool routes to support with your report attached.

What is not included yet

A few things are still deliberately out of scope:

  • automatic two-way sync with Google Contacts โ€” Tavina stays the source of truth, and changes made on Google’s side only come in when you run a refresh and approve them;
  • storing Gmail message bodies โ€” timelines keep only the subject, date, direction, and a one-line summary, by design.
  • writing back from CardDAV devices โ€” phone-side contact edits never flow into Tavina; CardDAV is read-only today, and writable sync is a planned later phase;
  • automatic call logging โ€” Tavina never reads your phone’s call log or records calls; call outcomes are entered by hand (see Calling from the app);
  • sending SMS โ€” the delivery layer is built email-first, and SMS is a planned later phase;

Recommended expectations

The Contacts tool is available in the dev channel and may still change. It is already useful as your primary address book: one record per person, per-channel consent you can trust, imports from files or Google Contacts with duplicate reporting, Gmail activity arriving on timelines by itself, reviewed merges, consent cleanup and export, read-only CardDAV so your iPhone’s Contacts app stays current, consent-gated email sending with unsubscribe and bounce protection, self-running email sequences whose exits are re-checked before every send, website intake on the dev channel, and agent help that respects your approval. Treat it as the single source of truth for people you know, and review agent proposals from the panel when they arrive.

Scroll to Top