Emmerdale viewers are turning detectives this week after Graham Foster was seen talking to a mysterious contact on the phone.
During Friday evening's episode, Graham (Andrew Scarborough) went behind Kim Tate's back again to make a secretive call where he could be heard saying: “We’ve got a problem, we’re going to need another plan.”
Some people originally presumed the unknown contact was Joe Tate (Ned Porteous), who was thought to have been murdered by Graham and Cain Dingle last October - although the body burial was never actually shown on screen.
But now fans of the ITV soap are saying that would be 'too obvious', and are convinced Kim's other son James was on the other end of the phone.
One viewer Tweeted: "Reckon it was James he was talking to, not Joe #emmerdale."
Another added: "Please let that phonecall mean Joe is still alive! It could have been Kim's son James Graham was talking to though. Hmmm..... #Emmerdale".
While a third echoed: "It’s not joe it’s james #Emmerdale."
Before Kim was sent back to prison in October she told Graham to find her son James after they became estranged.
So could Graham be hiding James from his mum to use at a later date? Or is Joe really still alive?
The mystery comes after Claire King - who plays Kim - teased James' return last year.
"He's bound to be young, glamorous, gorgeous – they're going to bring that kind of character in to replace Ned (Joe) aren't they?
"He'll be a good looking young boy. They haven't spoken for a while so that's why she's asked Graham to try and find James.
"There were very few people or things Kim genuinely loved last time – James was one, David [Glover] was another, Seth and her horses. And that was about it. She had total disrespect for anybody else in the whole world, she didn't care."
Emmerdale airs weekdays at 7pm on ITV, with an extra episode at 8pm on Thursdays.
Get the latest updates, reviews and unmissable series to watch and more!
Thank you for signing up to Whattowatch. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.