I have added this regex pattern in my training data file [1] [0-9]{9}$ This regex picks up possible outcomes like indian mobile numbers but the issue is it is not limiting the digit to 10 i.e if i enter like 12345 or even 123 it is taking it into slots also i have tested this regex here https://regex101.com/ pattern is working fine but i am facing issue with my bot 789 ↩︎

Can you post the regex section of your training data file?

"regex_features": [ { "name": "email", "pattern": "^([a-zA-Z0-9_\\-\\.]+)@([a-zA-Z0-9_\\-\\.]+)\\.([a-zA-Z]{2,5})$" }, { "name": "IncidentID", "pattern": "(?i)(SR)[0-9]*" }, { "name": "empCode", "pattern": "\\b\\d{8}\\b" }, { "name": "otp", "pattern": "\\b\\d{6}\\b" }, { "name": "MobNumberInt", "pattern": "[(+]*[0-9]{10}[()+. -]*" } ],

i am facing issue with mobile number regex pattern their are two mentioned both are facing this issue

I’m confused, I thought you said there was a problem with the number regex?

i have mentioned mobile numbers above, i want my bot to accept mobile numbers not random numbers like 123456 or anything of that sort! right now bot is accepting any numeric value into the slot

Can you also post what your training data looks like? Do you have any other shorter numbers that are present in it as well (doesn’t have to be the same entity)?

no in my training data for fetching mobile number i dont have less that 10 digit input.

training data - https://gist.github.com/NikhilBansal21/98028418102128453593a30885d38e1f

Ok so the thing is it doesn’t just pay attention to the actual word, but also the context. This is why it might accept shorter numbers too. Also you do have a short number as a mobile number entity towards the bottom of your training data. I saw that you have a lot of different numbers that you extract as different entities, my suggestion would be just to extract these with duckling and then store them in slots with a custom action. That way you can validate them to see if they’re in the correct format too

yes i added less digits because every time i enter like - U- my employee id is 9999852419 (a mobile number string) My bot picks up mobile number intent in this case which i don’t want my bot to do. even if user enters a mobile number in case of employee id or otp i want my bot to process it and guide user that input is wrong. Yes you are right i want it to handle at that context itself !

Regex pattern for mobile number not working properly

Rasa Open Source

souvikg10 (Souvik Ghosh) September 14, 2018, 9:04am 13

you need to provide the server for duckling

Topic		Replies	Views
RegexEntityExtrator and DIETClassifier extracting same intent and not following regex rule? Rasa Open Source	5	1752	June 21, 2021
Unable to use regex feature Rasa Open Source	7	2428	May 11, 2022
Similar Entity Extraction Rasa Open Source	18	2535	October 26, 2018
Storie test is failing in regex prediction Rasa Open Source testing	22	1072	July 2, 2021
Userwarning: Overlapping slot value Rasa Open Source	10	953	July 14, 2021

Regex pattern for mobile number not working properly

Related topics