Can't send texts to 88008 | iD Mobile Community
Skip to main content

Can't send texts to 88008

  • August 15, 2019
  • 7 replies
  • 649 views

HCHT
Community Member
  • Community Member
This issue is also present for cross country trains ten minute reservation system on 88008. Can ID do what ever needs to be done to add it their end?
This topic has been closed for replies.

7 replies

Ryan D
iD Mobile Employee
  • iD Mobile Employee
  • August 20, 2019
Hi there.

Have you ensured that the premium SMS feature is enabled within your account online and have you checked that you have enough of a billing cap to be able to send an SMS to this number?

Ryan

HCHT
Community Member
  • Author
  • Community Member
  • August 20, 2019
Yep

Ryan D
iD Mobile Employee
  • iD Mobile Employee
  • August 20, 2019
Hi @HCHT,

We can confirm that the number is already set up on our side. The texts look to cost at least £5.10 so we would advise you to up your cap, just in case it is near the limit.

Ryan

HCHT
Community Member
  • Author
  • Community Member
  • August 20, 2019
These are charges levied by who. Cross country trains say normal text cost.

Ryan D
iD Mobile Employee
  • iD Mobile Employee
  • August 21, 2019
Hi @HCHT,

From looking online, it seems that a Stroke charity also uses that number which is where that information came from. Are you ensuring that the message within the SMS contains the correct 'formula' in order for it to go through? Here is the Cross Country website which shows an example of what needs to be texted: https://www.crosscountrytrains.co.uk/tickets/ten-minute-reservations

I will however let our Tech Team know that Cross Country also use that number, in case this makes any difference.

Ryan

HCHT
Community Member
  • Author
  • Community Member
  • August 21, 2019
Yes itI works from both my work phones on EE, if you send an incorrect code they message back to say so. Complete mystery.

Kevin M
iD Mobile Employee
  • iD Mobile Employee
  • August 22, 2019
We'll keep an eye on this one from our office @HCHT we've put the question forward and someone from our Back Office Team is investigating this for us.

We should hopefully have an update in the next 3-5 working days, though hopefully sooner.