Found some similar posts for this problem:
Due to the fact that this posts were closed unresolved, I fear my requirement is unsolvable. Because I think that this would be an useful addition for many integrations, I should rather post a feature request, right?
I’d like to have some sort of intelligent filtering on this as well, but: this is probably hindered due to the various ways people are writing phone numbers as well as email signatures. It’d be easy if everyone strictly adhered to the formatting scheme in your example, but the same phone number might also be represented as variations of:
- Tel: 0049 123456789
- 0049 (0) 123 456 789
- +49 (0)123456789
- Phone: 0-123-456-789
(+49) 0 123 456 789
And if you take extension numbers or the addition of IVR menu choices into account (e.g. “press ‘2’ for billing”), it gets really weird and any regex used to filter out something that might resemble a telephone number will probably match a lot more than just a phone number.
Also: we have quite a few customers/companies who have emergency/standby or specialized numbers in their signatures, which should only be used in case of emergencies, or for specific purposes. All in all, this is very tricky to automate with filters.
I usually ask agents to be on the lookout for phone numbers in email signatures, and if these come by, have the agents check the customer’s profile if the number is already in their profile, and if it is still current (and if it is not in their profile or if it isn’t current, update the customer’s profile obviously). This is tedious work, but it does guarantee some level of consistency and uniform profile data, as we sanitize the formatting as well.
@dvanzuijlekom Thanks for your reply. Perhaps I misstated my goal a bit: I do not want the core team to add some automated magic to extract data from incoming emails. In fact I want the possibility to do it on my own: e.g. some kind of postmaster filter like [if mailbody regex ‘#phone:(?: )?(.*)’] [then] [modify ticket.customer.phone ‘$1’].
I am not aware of a configurable solution for your problem. But you can use the webhook feature to call a helper daemon (that you’ll need to write yourself) when a ticket is created. And that helper daemon then can update the user information using the REST-API of Zammad.
Maybe something like Huginn (open source alternative to IFTTT/Zapier) also can do the job.
@YetAnotherGerrit Thanks a lot for your hint. Maybe this can do the trick…
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.