Would Dynamic Objects work for our use case?

We’re very interested in leveraging the Dynamic Objects feature! 

The issue I’m running into is that our strings don’t have a static component like the ones shown in all examples.

To better clarify our instance, we use booking IDs that are composed of (currently) 6 digits (for example 123456). Booking IDs are assigned to bookings on an increasing basis (so the subsequent 2 bookings received would have IDs 123457 and 123458 respectively). I see also that strings cannot include spaces (so we wouldn’t be able to recognize strings from messages containing for example “I am asking about Booking 123456”). Occasionally, a customer may say “I am asking about Booking #123456”, in which case the static component of the string could be the #, however this would miss the vast majority of instances where the Dynamic Object could be applied.

Are there any solutions to this?

Thanks!