ChytryStart

A marketing team imports several thousand Czech contacts from an event registration into HubSpot. The registration form collected one free-text name field, so the data arrives as strings like "MUDr. Jana Svobodova" with the title fused to the name. An agent runs Analyze Full Name across the import, writes the separated first name, surname and titles back to their own properties, stores the vocative forms on the record, and populates the gender field that segmentation later depends on. The list stops being a pile of strings and becomes a set of records the campaign tooling can address correctly.

Name days matter in Czech and Slovak social convention in a way that has no direct English equivalent, and the date depends on the first name rather than on anything stored in the CRM. A scheduled agent runs Analyze Name Parts across the active customer base, reads back the Czech and Slovak name-day dates, and builds a calendar of who to greet and when. On the morning of each date the agent assembles the message using the vocative form already on the record and queues it in Brevo. The greeting arrives on the correct day, in the correct case, without anyone maintaining a lookup table.

A training provider issues completion certificates from a template. An agent reads the attendee record, calls Analyze Full Name to separate the academic title from the name, and passes both to APITemplate so the certificate prints the title in front of the name where Czech convention expects it. Where the title split is ambiguous, for example an unusual abbreviation the service did not recognize, the agent does not print its best guess. It holds that certificate out of the batch and asks the program coordinator to confirm the rendering before the run is released.