The Last Seen On field is a system-managed default contact field that automatically records the most recent time a contact interacted with your RapidPro.app workspace, and you can use it to find dormant contacts with search queries, build smart groups for re-engagement or cleanup, and schedule inactivity-based follow-ups in campaigns without manually updating the field.
You can manually create a contact in RapidPro.app when you need to add someone before they message you (for outreach, testing, or preparing data), by opening Contacts, creating a new contact, and saving at least one reachable address (URN)—typically a phone number in E.164 format with the country code—to ensure message delivery works correctly.
RapidPro.app lets you block contacts who abuse your service so they can no longer receive outbound messages and their inbound messages are automatically archived, and you can do this either manually from the Contacts list (and later unblock from the Blocked view) or automatically in a flow by setting Update Contact → Status to Blocked when you detect spam or offensive content.
Contact fields store structured information about each contact, and the Manage Contact Fields page lets you create, edit, and remove fields, control whether they are featured, set agent visibility/edit access, and understand where fields are used (including fields created from flows via Update Contact actions).
Contact fields are empty by default until you set values through an import, a flow, or manual edits on the contact profile, so updating fields (like Name or project-specific custom fields) helps you identify contacts correctly and power automation—most commonly by using Update Contact inside a flow, or by editing the contact directly from the Contacts tab.
Bulk importing contacts lets you add or update many contacts at once in RapidPro.app using an XLS/XLSX spreadsheet, including names, addresses (URNs) like phone numbers in E.164 format, optional language and custom fields, and—when updating existing contacts—UUIDs to ensure records are updated correctly instead of creating duplicates.
Deleting contacts in RapidPro.app is permanent, so you can only delete a contact after moving them to the Archived folder—either by archiving an individual contact manually and then deleting it from Archived, or by archiving a whole group via a flow (Status = Archived) and using Delete All in the Archived folder after you’ve reviewed the list.
Custom contact fields let you store project-specific information on contacts beyond the built-in fields, by creating fields in Contacts → Fields (choosing the correct type like Text, Number, or Date & Time, setting agent access, and optionally featuring the field), then using the field reference in flows (for example via Update Contact with @results variables) so data stays consistent across messages, exports, and automation.
RapidPro.app lets you search contacts using query expressions based on names, URNs, and contact field values, which you can use in the Contacts search bar, the Start Flow dialog, and Smart Groups to segment audiences, find missing or inactive records, and power automation with logical operators and field-type-aware comparisons.
Contact Information Anonymization permanently removes personally identifiable information (PII) from contacts—such as names and addresses (URNs)—while keeping operational data like UUID, groups, language, and custom fields usable for segmentation, flows, campaigns, and anonymized exports, making it suitable for privacy-first or compliance-driven programs where identities aren’t required for operations.
